mdconfig

[sbremal at hotmail.com]

Hello

Wonder if there should be any consistency in 'mdconfig' parameter parsing when run from the shell and when run through 'rc.conf'.

I hoped I could copy'n'paste the parameters from the command line to 'rc.conf', reboot and enjoy. No.


Works fine from command line:

mdconfig -f /usr/local/zfs/backups -u 0


Fails in 'rc.conf', the file is surely there:

mdconfig_md0="-f /usr/local/zfs/backups"

kernel: Creating md0 device (-f).
kernel: mdconfig:
kernel: could not find full path for /usr/local/zfs/backups
kernel: :
kernel: No such file or directory
kernel: Creating md0 device failed, moving on.


Also fails:

mdconfig_md0="-f /usr/local/zfs/backups -t vnode"

kernel: Creating md0 device (vnode).
kernel: usage: mdconfig -a -t type [-n] [-o [no]option] ... [-f file]
kernel: [-s size] [-S sectorsize] [-u unit]
kernel: [-x sectors/track] [-y heads/cyl]
kernel: mdconfig -d -u unit [-o [no]force]
kernel: mdconfig -l [-v] [-n] [-u unit]
kernel: type = {malloc, preload, vnode, swap}
kernel: option = {cluster, compress, reserve}
kernel: size = %d (512 byte blocks), %db (B),
kernel: %dk (kB), %dm (MB), %dg (GB) or
kernel: %dt (TB)
kernel: Creating md0 device failed, moving on.


Works:

mdconfig_md0="-t vnode -f /usr/local/zfs/backups"

kernel: Creating md0 device (vnode).
kernel: fsck:


Would anyone bother make 'rc.conf' more relaxed about the parameters and their order?


Cheers
Balazs

---

man mdconfig
...
-f file
        Filename to use for the vnode type memory disk. Options -a and -t
        vnode are implied if not specified.
...

man rc.conf
...
     mdconfig_md<X>
                 (str) Arguments to mdconfig(8) for md(4) device X.  At mini-
                 mum a -t type must be specified and either a -s size for mal-
                 loc or swap backed md(4) devices or a -f file for vnode
                 backed md(4) devices.  Note that mdconfig_md<X> variables are
                 evaluated until one variable is unset or null.
...