Date: Sat, 14 Jul 2007 09:52:19 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com> Cc: Volker <volker@vwsoft.com>, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: zfs refuses to load pool on boot, zpool denies import Message-ID: <20070714145219.GH44766@dan.emsphone.com> In-Reply-To: <200707141107.48714.Thomas.Sparrevohn@btinternet.com> References: <4697F753.5060304@vwsoft.com> <20070713221854.GC44766@dan.emsphone.com> <4698005B.3010100@vwsoft.com> <200707141107.48714.Thomas.Sparrevohn@btinternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 14), Thomas Sparrevohn said: > On Friday 13 July 2007 23:44:43 Volker wrote: > > damned... that's it. Thanks a lot. I was wondering about that > > because I've already seen a system uuid in kenv (only checked > > smbios.system.uuid) while in single user mode so I did not see the > > need to manually fire `/etc/rc.d/hostid start'. > > > > This may be taken into the documentation - I guess more will step into > > this. > > > > Or what about checking the hostid before doing any `zpool create | > > import' and refuse operation (with a useful hint to the operator) if > > hostid is 0x0? That would be useful.. > I got burned by that one as well - I am vondering if ZFS should check > system.uuid as a fall back - It does not seem correct that we have to > run specific startup shell scripts in order to get a filesystem to > work Might work in some cases, but none of my systems have the system.uuid kenv. I'm not even sure how my zfs root volume gets mounted; the kernel has to mount it to even find init, so it does blindly mount zpools in some cases. Maybe the kernl mount logic assumes if it can only see one zpool, it's got to be the right one? :) -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070714145219.GH44766>