Hello eric, Wednesday, October 10, 2007, 7:31:04 PM, you wrote:
ek> On Oct 10, 2007, at 11:23 AM, Bernhard Duebi wrote: >> Hi everybody, >> >> I tested the following scenario: >> >> I have two machine attached to the same SAN LUN. >> Both machines run Solaris 10 Update 4. >> Machine A is active with zpool01 imported. >> Machine B is inactive. >> Machine A crashes. >> Machine B imports zpool01 >> Machine A comes back >> >> Now the problem is, that when machine A comes back, it imports >> zpool01 even if it belongs to machine B now. >> I've seen this problem some time ago in a blog, but don't remember >> where. Will this be fixed ? ek> See: ek> http://blogs.sun.com/erickustarz/entry/poor_man_s_cluster_end ek> The changes are already in OpenSolaris, and will make it in s10u5. In a way he could workaround it today - manually imporot pool with -R option. It means that everytime server reboots you will have to manually import a pool but at least you won't endup with two hosts with the same pool. You could also write a script to import a pool with -R but without forcr option. So during normal (clean) reboots a pool will be imported automatically. Or if you already have two servers in a SAN, just grab Sun Cluster 3.2 which is for free (if you don't need a support) and use it. Works with no problems with zfs. -- Best regards, Robert Milkowski mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
