+1
On Mon, Mar 23, 2009 at 8:43 PM, Damon Atkins wrote:
> PS it would be nice to have a zpool diskinfo reports if the
> device belongs to a zpool imported or not, and all the details about any
> zpool it can find on the disk. e.g. file-systems (zdb is only for ZFS
> "engineers" says the man pa
The zpool.cache file makes clustering complex. {Assume the man page is
still correct}
From the zpool man page:
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 tha
Damon Atkins wrote:
The zpool.cache file makes clustering complex. {Assume the man page is
still correct}
The man page is correct. zpool.cache helps make clustering feasible
because it differentiates those file systems which are of interest from
those which are not. This is particularly impor
The zpool.cache file makes clustering complex. {Assume the man page is
still correct}
From the zpool man page:
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
