[DRBD-user] Dual Primary Mode: Shared Directory blocked after node crash until reboot

DRBD User DRBDUser at gmx.at
Mon May 11 11:20:55 CEST 2015

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

I have configured these handlers:

fence-peer: /usr/lib/drbd/crm-fence-peer.sh;
after-resync-target: /usr/lib/drbd/crm-unfence-peer.sh;
split-brain: /usr/lib/drbd/notify-split-brain.sh;

pacemakers pcs property stonith-enabled is currently set to false

I do a synchronization of 2 services using a lck file in the shared directory.

If one service can lock the lck file, it becomes master service and can serialize its status in the shared directory.

If one service dies, the other service can take over the work (lock the lck file, deserialize the status, ...)

When i stop the node running the master service using 'pcs cluster standby node2', the shared directory is accessible on node1 and the service on node1 becomes master - but if i do a power plug pull i have to wait the reboot time, until the (new) master service has access to the shared directory.

1) >>> Without successful fencing, the only safe option is to lock up
How do i do this ?

2) It is possible to define the time when an active node gets informed about another node crash (currently it takes about 2sec before DRBD changes the status of the crashed node) ?

More information about the drbd-user mailing list