Suppose that you have a SAN environment with a lot of LUNs. In the
normal course of events this means that 'zpool import' is very slow,
because it has to probe all of the LUNs all of the time.

 In S10U6, the theoretical 'obvious' way to get around this for your
SAN filesystems seems to be to use a non-default cachefile (likely one
cachefile per virtual fileserver, although you could go all the way to
one cachefile per pool) and then copy this cachefile from the master
host to all of your other hosts. When you need to rapidly bring up a
virtual fileserver on a non-default host, you can just run
        zpool import -c /where/ever/<host>.cache -a

 However, the S10U6 zpool documentation doesn't say if zpool cachefiles
can be copied between systems and used like this. Does anyone know if
this is a guaranteed property that is sure to keep working, something
that works right now but there's no guarantees that it will keep working
in future versions of Solaris and patches, or something that doesn't
work reliably in general?

(I have done basic tests with my S10U6 test machine, and it seems to
work ... but I might easily be missing something that makes it not
reliable.)

        - cks
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to