Hello! Heading the DRBD Guide for DRBD with OCFS (with pacemaker), it suggests that fencing needs to be done whenever there is a problem with one of the nodes running DRBD.
I really wonder why: Why shoot the node if one out of several resources has a problem? Why not try a disconnect/reconnect first? It should be faster anyway. Also if you are using different networks for cluster, access, and replication, why assume that the cluster communication is dead if one DRBD resource has a problem? While it may sound increadibly cool for the developers to reset any node in the cluster, this is the most annoying thing in practice, especially as you have little chances for debugging the problems. Would someone explain the rationale behind? Regards, Ulrich _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
