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 GaponReceived on Fri Oct 16 2009 - 06:28:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:57 UTC