> There are times when a cluster might try a simple > import, and there > are times when a cluster will force the import. We > do know that if > two nodes have simultaneously imported the pool then > chances are > very good that the pool will be corrupted. So it > seems prudent for > the cluster to make the decision to force the import > (as Solaris Cluster > and Clustron do). For humans, the -f flag seems to > help keep them > out of trouble. > -- richard
Sun cluster does not provide any help in this case. The problem is located inside the logical domain. SUN cluster supports the changeover of ldom between execution hosts and works fine at all. But after changeover a ldom inherits the hostid of the current execution host. After binding and rebooting the automated 'zpool import' inside this ldom fails based on the fact that the same virtual server has a new hostid. The zpool which can not be imported is never out in the open and can be in use from this virtual server only. In future, if ldoms can use zfs/zpool as boot disk our problem can turn nasty. http://www.opensolaris.org/jive/thread.jspa?messageID=311019񋻫 torsten -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
