Date: Fri, 16 Oct 2009 11:28:01 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, Anonymous <swell.k@gmail.com>, freebsd-current@FreeBSD.org Subject: Re: zfs boot vs loader Message-ID: <4AD82E91.3030703@icyb.net.ua> In-Reply-To: <20091014062827.GC1696@garage.freebsd.pl> References: <4AD3220B.5030502@icyb.net.ua> <86ws30ikfw.fsf@gmail.com> <4AD45A8D.4070605@icyb.net.ua> <20091014062827.GC1696@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
on 14/10/2009 09:28 Pawel Jakub Dawidek said the following: > On Tue, Oct 13, 2009 at 01:46:37PM +0300, Andriy Gapon wrote: >> Thanks to all who replied! >> I think that I figured it out with your help. >> >> 'unload' does indeed unload zpool.cache and the latter is needed for proper zfs >> root mounting. >> 'boot /other/kernel' executes some loader scripts and zpool.cache gets loaded in >> this case (because of the settings in defaults/loader.conf). >> When doing manual 'load xxx' and then just 'boot' no loader scripts are executed >> and zpool.cache does not get loaded. In this case one has to load it manually >> using the suggested 'load -t xxx' approach. > > Could you repeat what you were doing but with vfs.zfs.debug set to 1 > from the loader? You should see some messages about missing file, maybe > we should do them visible always and not after increasing debug level? Yes, I tried this and got the following message: spa_config_load:92[1]: Cannot open /boot/zfs/zpool.cache Perhaps it's a good idea indeed to be more verbose about this. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AD82E91.3030703>