Date: Wed, 30 Jan 2008 16:28:02 -0500 From: James Snow <snow@teardrop.org> To: freebsd-current@freebsd.org Subject: Re: ZVOL/ZFS hosting UFS filesystems ... ERROR! Message-ID: <20080130212801.GA90184@teardrop.org> In-Reply-To: <86hcn34gss.fsf@ds4.des.no> References: <20070813055415.GM93381@obelix.dsto.defence.gov.au> <790a9fff0708122350w729761d1v72e6aaff414d3756@mail.gmail.com> <20070813070530.GT93381@obelix.dsto.defence.gov.au> <20070813123332.bd6dba7b.gary.jennejohn@freenet.de> <861we75zn6.fsf@ds4.des.no> <20070813134439.GX93381@obelix.dsto.defence.gov.au> <86hcn34gss.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
I realize I'm picking up an old thread, but I was having the same problem. Quick recap: Create a UFS filesystem on a ZVOL, drop an entry in /etc/fstab, and fail to mount the UFS/ZVOL filesystem at boot even if you add 'late' to the options in /etc/fstab. On Mon, Aug 13, 2007 at 05:04:19PM +0200, Dag-Erling Sm??rgrav wrote: > "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> writes: > > > However, having said that, /etc/rc.d/zfs is before /etc/rc.d/mountlate. > > so everything is fine? > > > Suggestions ? > > If it still doesn't work, I'll need to see the full console output from > the point where init(8) starts until the point where getty(8) starts. For me the trouble was /etc/rc.d/fsck. fsck runs before zfs and mountlate, fails to find the UFS/ZVOL filesystem, and aborts the boot process. You can work around this by setting pass# to 0 in /etc/fstab. The trouble with this approach is that since this is a UFS filesystem, ZVOL or not, I'd still like to fsck it. -Snow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080130212801.GA90184>