On 19/04/2010 16:46, Don wrote:
I want to know if there is a way for a second node- connected to
> a set of shared disks- to keep its zpool.cache up to date
> _without_ actually importing the ZFS pool.
See zpool(1M):
cachefile=path | none
Controls the location of where the pool configuration is
cached. Discovering all pools on system startup requires
a cached copy of the configuration data that is stored
on the root file system. All pools in this cache are
automatically imported when the system boots. Some
environments, such as install and clustering, need to
cache this information in a different location so that
pools are not automatically imported. Setting this pro-
perty caches the pool configuration in a different loca-
tion that can later be imported with "zpool import -c".
Setting it to the special value "none" creates a tem-
porary pool that is never cached, and the special value
'' (empty string) uses the default location.
Multiple pools can share the same cache file. Because
the kernel destroys and recreates this file when pools
are added and removed, care should be taken when
attempting to access this file. When the last pool using
a cachefile is exported or destroyed, the file is
removed.
--
Darren J Moffat
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
