Hello Paul, Monday, February 26, 2007, 8:28:43 PM, you wrote:
>> From: Eric Schrock [mailto:[EMAIL PROTECTED] >> Sent: Monday, February 26, 2007 12:05 PM >> >> The slow part of zpool import is actually discovering the >> pool configuration. This involves examining every device on >> the system (or every device within a 'import -d' directory) >> and seeing if it has any labels. Internally, the import >> action itself shoudl be quite fast... PF> Thanks for the answer. Let me ask a follow-up question related PF> to zpool import and the sun cluster+zfs integration -- is the slow PF> part done "early" on the backup node so that at the time of the PF> failover the actual import is "fast" as you describe above? Right now Sun Cluster does import almost the same way as 'zpool import' does. Perhaps SC could save config for each pool and then during import use it in a similar way zpool.cache is used during zfs initialization but only for a given pool. In most cases it should greatly reduce import time in SC environment with lot of LUNs. Perhaps: zpool config export pool >pool.cache then later - zpool import -c pool.cache pool Of course such imported pool won't be added to zpool.cache (or perhaps it should be optional and SC doesn't used zpool command anyway). -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
