On 08/30/2011 04:59 AM, "Hung-Sheng Tsao (Lao Tsao 老曹) Ph.D." wrote:


IMHO, you need to know how to recover the Zpool if the data/metadata get corrupt due to import by two hosts
may be things are improved for zfs recently.
you design cluster by certain rules, hope that all SA(not just you) will follow your rules, otherwise some SA may just import zpool that create cachefile and next time the system will want to import the zpool in cachefile that already imported by other hosts Sun cluster use its own cachefile to control the cache, but as any design it could not prevent SA to import zpool by hand:-(

ZFS has some safeguards to protect against this error -- but those safeguards are bypassed when using "-f" to import a pool. Its absolutely vital that system administrators are taught to try without -f first, and the only use -f to import a pool when they are *absolutely certain* that no other system can be accessing the pool concurrently.

Clusters require a greater degree of care and skill than ordinary systems. This is one reason that I try to steer folks towards application redundancy rather than cluster configurations, when redundancy at the application layer is available.

    - Garrett

my 2c

On 8/29/2011 9:03 PM, Gary Mills wrote:
On Mon, Aug 29, 2011 at 07:56:16PM -0400, LaoTsao wrote:
Q?
are you intent to import this zpool to different host?
Yes, it can be imported on another server.  That part works when it
has been exported cleanly first.  I was concerned about a possible
import failure when the original server lost power.

Sent from my iPad
Sent from my Sun type 6 keyboard.


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

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

Reply via email to