From owner-freebsd-bugs@FreeBSD.ORG Tue Jul 16 15:23:25 2013 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E3D60D19 for ; Tue, 16 Jul 2013 15:23:25 +0000 (UTC) (envelope-from sbremal@hotmail.com) Received: from dub0-omc4-s13.dub0.hotmail.com (dub0-omc4-s13.dub0.hotmail.com [157.55.2.88]) by mx1.freebsd.org (Postfix) with ESMTP id 8D67EDFC for ; Tue, 16 Jul 2013 15:23:25 +0000 (UTC) Received: from DUB104-W24 ([157.55.2.71]) by dub0-omc4-s13.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 16 Jul 2013 08:22:18 -0700 X-TMN: [2PXBWNzvpsL87ZuWGXwc1d4oHJTWelbi] X-Originating-Email: [sbremal@hotmail.com] Message-ID: From: To: "freebsd-bugs@freebsd.org" Subject: mdconfig Date: Tue, 16 Jul 2013 15:22:18 +0000 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 16 Jul 2013 15:22:18.0439 (UTC) FILETIME=[426AAD70:01CE8238] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 15:23:26 -0000 Hello=0A= =0A= Wonder if there should be any consistency in 'mdconfig' parameter parsing w= hen run from the shell and when run through 'rc.conf'.=0A= =0A= I hoped I could copy'n'paste the parameters from the command line to 'rc.co= nf'=2C reboot and enjoy. No.=0A= =0A= =0A= Works fine from command line:=0A= =0A= mdconfig -f /usr/local/zfs/backups -u 0=0A= =0A= =0A= Fails in 'rc.conf'=2C the file is surely there:=0A= =0A= mdconfig_md0=3D"-f /usr/local/zfs/backups"=0A= =0A= kernel: Creating md0 device (-f).=0A= kernel: mdconfig:=0A= kernel: could not find full path for /usr/local/zfs/backups=0A= kernel: :=0A= kernel: No such file or directory=0A= kernel: Creating md0 device failed=2C moving on.=0A= =0A= =0A= Also fails:=0A= =0A= mdconfig_md0=3D"-f /usr/local/zfs/backups -t vnode"=0A= =0A= kernel: Creating md0 device (vnode).=0A= kernel: usage: mdconfig -a -t type [-n] [-o [no]option] ... [-f file]=0A= kernel: [-s size] [-S sectorsize] [-u unit]=0A= kernel: [-x sectors/track] [-y heads/cyl]=0A= kernel: mdconfig -d -u unit [-o [no]force]=0A= kernel: mdconfig -l [-v] [-n] [-u unit]=0A= kernel: type =3D {malloc=2C preload=2C vnode=2C swap}=0A= kernel: option =3D {cluster=2C compress=2C reserve}=0A= kernel: size =3D %d (512 byte blocks)=2C %db (B)=2C=0A= kernel: %dk (kB)=2C %dm (MB)=2C %dg (GB) or=0A= kernel: %dt (TB)=0A= kernel: Creating md0 device failed=2C moving on.=0A= =0A= =0A= Works:=0A= =0A= mdconfig_md0=3D"-t vnode -f /usr/local/zfs/backups"=0A= =0A= kernel: Creating md0 device (vnode).=0A= kernel: fsck:=0A= =0A= =0A= Would anyone bother make 'rc.conf' more relaxed about the parameters and th= eir order?=0A= =0A= =0A= Cheers=0A= Balazs=0A= =0A= ---=0A= =0A= man mdconfig=0A= ...=0A= -f file=0A= Filename to use for the vnode type memory disk. Options -a and -t= =0A= vnode are implied if not specified.=0A= ...=0A= =0A= man rc.conf=0A= ...=0A= mdconfig_md=0A= (str) Arguments to mdconfig(8) for md(4) device X. At min= i-=0A= mum a -t type must be specified and either a -s size for m= al-=0A= loc or swap backed md(4) devices or a -f file for vnode=0A= backed md(4) devices. Note that mdconfig_md variables = are=0A= evaluated until one variable is unset or null.=0A= ... =