[DRBD-user] Corosync and DRBD fencing: one or both?

Digimer linux at alteeve.com
Mon Aug 29 22:42:10 CEST 2011

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

On 08/29/2011 03:36 PM, William Seligman wrote:
> A general question: I have a Corosync+Pacemaker with DRBD setup on Linux; I'll
> give the details if it's relevant. Corosync+Pacemaker controls DRBD start, stop,
> and promotion. I've implemented fencing via STONITH as Corosync resources.
> I have not put fencing in the drbd.conf file; I was under the impression that
> Corosync+Pacemaker would take of STONITHing a node if there's a DRBD problem. Is
> this correct? Or should I have fencing/STONITH configured in both Corosync and
> drbd.conf?
> Does the answer change between a primary/secondary versus dual-primary setup?

You still want to configure fencing, but you can use the
'crm-fence-peer.sh' handler. Using this with 'resource-and-stonith' will
tell DRBD to block I/O until the fence succeeds, preventing it from
going dual-primary (even if just for the brief moment between fault and

E-Mail:              digimer at alteeve.com
Freenode handle:     digimer
Papers and Projects: http://alteeve.com
Node Assassin:       http://nodeassassin.org
"At what point did we forget that the Space Shuttle was, essentially,
a program that strapped human beings to an explosion and tried to stab
through the sky with fire and math?"

More information about the drbd-user mailing list