[DRBD-user] drbd on heartbeat links

Pavlos Parissis pavlos.parissis at gmail.com
Tue Nov 2 16:07:16 CET 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


I am trying to figure out how I can resolve the following scenario

3 nodes
2 DRBD ms resource
2 group resource
by default drbd1/group1 runs on node-01 and drbd2/group2 runs on node2
drbd1/group1  can only run on node-01 and node-03
drbd2/group2  can only run on node-02 and node-03
DRBD fencing_policy is resource-only [1]
2 heartbeat links and one of them used by DRBD communication

1) node-01 loses both heartbeat links
2) DRBD monitor detects first the absence of the drbd communication
and does resource fencing by add location constraint which prevent
drbd1 to run on node3
3) pacemaker fencing kicks in and kills node-01

due to location constraint created at step 2, drbd1/group1 can run in
the cluster

Any ideas?


[1] it is not resource-and-stonith because in the scenario where a
node has the role of primary for drbd1 and secondary for drbd2, could
be fenced because the primary node of drbd2 have in fencing_policy

More information about the drbd-user mailing list