Hi One thing bothers me again : I have this record in cluster.conf : <quorumd label="QDISK_0_0" interval="1" tko="10" votes="1" min_score="1"> <heuristic interval="10" tko="3" program="ping -t1 -c1 172.20.0.110" score="1"/> <heuristic interval="10" program="ping -t3 -c1 172.20.0.110" score="1"/> </quorumd> where 172.20.0.110 is a third machine not in my cluster pair node1/node2 My last understanding was that quorum disk was NOT a redundancy of heart-beat, meaning that if heart-beat interface fails, there is a failover but it is always the node with the expected min_score in quorum disk which fence the other. So I thought that the quorum disk check was operationnal only if the node detects a problem on heart-beat interface ... but when I set down the interface on the third machine, and after a few seconds, both nodes node1/node2 are killed !!! Whereas heart-beat interface was working fine. And after reboot, I can see "cluster not quorate" etc. So in fact, even if the heart-beat interface works fine, but there is not the expected min_score for heuristics of quorum disk, both nodes are stopped. Is it the normal behavior ? Thanks Regards Alain Moullé -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
