On 03/31/10 03:50 AM, Damon Atkins wrote:
Why do we still need "/etc/zfs/zpool.cache" file???
(I could understand it was useful when zfs import was slow)
zpool import is now multi-threaded
(http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6844191), hence a
lot faster, each disk contains the hostname
(http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6282725) , if a
pool contains the same hostname as the server then import it.
ie This bug should not be a problem any more
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6737296 with a
multi-threaded zpool import.
HA Storage should be changed to just do a zpool -h import mypool instead of
using a private zpool.cache file (-h being ignore if the pool was imported by a
different host, and maybe a noautoimport property is need on a zpool so
clustering software can decided to import it by hand as it was)
And therefore this zpool zplit problem would be fixed.
The problem with splitting a root pool goes beyond the issue of the
zpool.cache file. If you look at the comments for 6939334
<http://monaco.sfbay.sun.com/detail.jsf?cr=6939334>, you will see other
files whose content is not correct when a root pool is renamed or split.
I'm not questioning your logic about whether zpool.cache is still
needed. I'm only pointing out that eliminating the zpool.cache file
would not enable root pools to be split. More work is required for that.
Lori
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
