Date: Thu, 31 Jan 2008 17:14:40 -0500 From: James Snow <snow+freebsd-current@teardrop.org> To: freebsd-current@freebsd.org Subject: Re: ZVOL/ZFS hosting UFS filesystems ... ERROR! Message-ID: <20080131221440.GC1926@teardrop.org> In-Reply-To: <20080130212801.GA90184@teardrop.org> 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> <20080130212801.GA90184@teardrop.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 30, 2008 at 04:28:02PM -0500, James Snow wrote: > > 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. swell.k@gmail.com wrote to me and suggested the following fix: --- /usr/src/etc/rc.d/hostid +++ /etc/rc.d/hostid @@ -28,7 +28,7 @@ # # PROVIDE: hostid -# REQUIRE: root +# REQUIRE: early # BEFORE: mountcritlocal # KEYWORD: nojail --- /usr/src/etc/rc.d/zfs +++ /etc/rc.d/zfs @@ -4,7 +4,7 @@ # # PROVIDE: zfs -# REQUIRE: mountcritlocal +# REQUIRE: hostid This puts /etc/rc.d/zfs before /etc/rc.d/fsck in the boot process, which fixes the problem perfectly. There don't appear to be any unintended consequences that I can see. -Snow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080131221440.GC1926>