Mathias F wrote:
I think I get the whole picture, let me summarise:
- you create a pool P and an FS on host A
- Host A crashes
- you import P on host B; this only works with -f, as
"zpool import" otherwise
refuses to do so.
- now P is imported on B
- host A comes back up and re-accesses P, thereby
leading to (potential)
corruption.
- your hope was that when host A comes back, there
exists a mechanism for
telling it "you need to re-import".
- Vxvm, as you currently use it, has this
functionality
Is that correct?
Yes it is, you got it ;)
VxVM just notices that it's previously imported DiskGroup(s) (for ZFS this is
the Pool) were failed over and doesn't try to re-acquire them. It waits for an
admin action.
The topic of "clustering" ZFS is not the problem atm, we just test the failover
behaviour manually.
well, I think nevertheless you'll have to wait for SunCluster 3.2 for this to
work. As others have said, ZFS as is currently is not made to work as you
expect it to.
regards
--
Michael Schuster +49 89 46008-2974 / x62974
visit the online support center: http://www.sun.com/osc/
Recursion, n.: see 'Recursion'
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
