jan damborsky wrote: > Hi Sanjay, > > > jan damborsky wrote: >>> 326-336 - can you verify that this is needed with the changes for zfs >>> boot. >> I have removed all code dealing with "zpool.cache" file. That code >> originally took care of having etc/zfs/zpool.cache in list of files >> which need to be in boot archive. I have installed 91 on ZFS root >> and zpool.cache is not being added in filelist.ramdisk and is not >> part of boot archive. > > Searching more, I have found appropriate section in > PSARC/2006/370 - ZFS as a Root File System referring to this: > > "Early in the kernel startup stage, before the zfs root file can be > mounted, the state of the root pool must be imported. The zpool.cache > file cannot be read at this time because it isn't in the boot archive > (see PSARC/2006/525 - Newboot Sparc). However, the information for the > root pool is available in the metadata stored in the boot disk (which, > by definition, is a vdev in the root pool). So the metadata used to > make the root pool active is read directly from the boot disk." > > However, looking at the LiveCD, filelist.ramdisk contains > entry for "etc/zfs/zpool.cache" file: > > $ grep zfs /boot/solaris/filelist.ramdisk > etc/zfs/zpool.cache > > So, it seems that more changes would need to be done on LiveCD > and in Slim install with respect to the integration of ZFS root > project. I have also noticed following when looking at nv91 > installed on ZFS root using SXCE text installer: > > * root is no longer "legacy" mounted > * swap & dump are on ZFS volumes > > That said, these are not directly related to the "GRUB" issue > addressed by the fix, but should I file new CR to address all > remaining ZFS root changes ? >
Yes, I would like these addressed soon. Dave
