hi there,
On Thu, 2007-07-26 at 21:51 +0800, Andre Wenas wrote:
> You need to specify your boot zfs pool in grub menu.lst:
Hang on, I'm not sure that was the point of the question.
> Robert Prus - Solution Architect, Systems Practice - Sun Poland wrote:
> > Where from Solaris/ZFS knows which storage pools/datasets should be
> > mounted after reboot???
The pool data is cached in a binary file /etc/zfs/zpool.cache. This
determines which pools are visible to the system.
> > ZFS is not using at all /etc/vfstab configuration file (I exclude here
> > case where we set mountpoint=legacy).
Right.
> > My understanding is that ZFS kernel modules are writing some information
> > about mounting state of storage pools/datasets to disks just before
> > unloading (of ZFS kernel modules).
If a given pool is visible to the system, then if the "mountpoint"
property is set to something other than "legacy" or "none", then this is
mounted at boot (unless the "canmount" property is set to off, if that's
available in the version of ZFS you're looking at)
This is documented in the ZFS man page.
> When Solaris boots, it is loading ZFS
> > kernel modules. These kernel modules are checking all disks devices in
> > /dev, /devices directories for possibility of performing silent 'zpool
> > import -a'.
Not so - we don't do a zpool import -a, rather we go on the zpool.cache
file. If that file isn't present, you'll need to manually zpool import
pools in order for the system to see them.
cheers,
tim
--
Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops
http://blogs.sun.com/timf
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
