On Sep 13, 2006, at 12:32 PM, Eric Schrock wrote:
Storing the hostid as a last-ditch check for administrative error is a
reasonable RFE - just one that we haven't yet gotten around to.
Claiming that it will solve the clustering problem oversimplifies the
problem and will lead to people who think they have a 'safe' homegrown
failover when in reality the right sequence of actions will
irrevocably
corrupt their data.
HostID is handy, but it'll only tell you who MIGHT or MIGHT NOT have
control of the pool.
Such an RFE would even more worthwhile if it included something such
as a time stamp. This time stamp (or similar time-oriented signature)
would be updated regularly (bases on some internal ZFS event). If
this stamp goes for an arbitrary length of time without being
updated, another host in the cluster could force import it on the
assumption that the original host is no longer able to communicate to
the zpool.
This is a simple idea description, but perhaps worthwhile if you're
already going to change the label structure for adding the hostid.
/dale
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss