On September 13, 2006 6:09:50 AM -0700 Mathias F
<[EMAIL PROTECTED]> wrote:
[...]
a product which is *not* currently multi-host-aware to
behave in the
same safe manner as one which is.
That`s the point we figured out while testing it ;)
I just wanted to have our thoughts reviewed by other ZFS users.
Our next steps IF the failover would have succeeded would be to create a
little ZFS-agent for a VCS testing cluster. We haven't used Sun Cluster
and won't use it in future.
/etc/zfs/zpool.cache is used at boot time to find what pools to import.
Remove it when the system boots and after it goes down and comes back
up it won't import any pools. Not quite the same as not importing if
they are imported elsewhere, but perhaps close enough for you.
On September 13, 2006 10:15:28 PM +1000 "James C. McPherson"
<[EMAIL PROTECTED]> wrote:
As I understand things, SunCluster 3.2 is expected to have support for
HA-ZFS
and until that version is released you will not be running in a supported
configuration.... and so any errors you encounter are *your fault alone*.
Didn't we have the PMC (poor man's cluster) talk last week as well?
I understand the objection to mickey mouse configurations, but I don't
understand the objection to (what I consider) simply improving safety.
Why again shouldn't zfs have a hostid written into the pool, to prevent
import if the hostid doesn't match?
And why should failover be limited to SC? Why shouldn't VCS be able to
play? Why should SC have secrets on how to do failover? After all,
this is OPENsolaris. And anyway many homegrown solutions (the kind
I'm familiar with anyway) are of high quality compared to commercial
ones.
-frank
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
