Date: Thu, 18 Nov 2010 10:58:17 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: Garrett Cooper <yanegomi@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic with vfs.root.mountfrom=nfs on CURRENT (was Re: [patch] functional prototype of root mount enhancement) Message-ID: <5ED46E71-B0C1-459E-976C-D64234002F03@mac.com> In-Reply-To: <AANLkTi=cZL5Sqr-tHcP-sh6URL2QHB41JkFxvJM_uK0A@mail.gmail.com> References: <AANLkTi=cZL5Sqr-tHcP-sh6URL2QHB41JkFxvJM_uK0A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 17, 2010, at 4:10 PM, Garrett Cooper wrote: > > Hi Marcel, > Do you have any examples that use nfs rootfs's out of the box that > work with the new logic that don't involve creating an mfsroot? I keep > on running into this error with vfs.root.mountfrom=nfs (previously on > CURRENT it would just try to mount nfs via nfs_mount in the NFS client > without any complaints): The syntax is $fs:$dev. For NFS $dev can be empty, leaving "nfs:". The problem is with there not being a colon after nfs in your case. This could be a change in behaviour from before, which probably needs a fix. I'll look into it... > I don't run into this error when I unset this variable sometimes > (it boots up multiuser and all is happy, hunky dory when I manually > query this variable from the pxeboot loader, but not when I don't... > it's weird). > It seems to ignore the directives in mount.conf: > > # cat mount.conf > .onfail continue > .ask The filename to use is "/.mount.conf". Notice the period. -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ED46E71-B0C1-459E-976C-D64234002F03>