[Pacemaker] drbd-fence-by-handler

Jake Smith jsmith at argotec.com
Mon Jun 17 12:37:49 EDT 2013


----- Original Message -----
> From: "andreas graeper" <agraeper at googlemail.com>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Monday, June 17, 2013 12:16:11 PM
> Subject: [Pacemaker] drbd-fence-by-handler
> 
> 
> 
> 
> 
> 
> hi,
> 
> <rsc_location rsc="ms_drbd" id="drbd-fence-by-handler-r0-ms_drbd">
> <rule role="Master" score="-INFINITY"
> id="drbd-fence-by-handler-r0-rule-ms_drbd">
> <expression attribute="#uname" operation="ne" value="n1"
> id="drbd-fence-by-handler-r0-expr-ms_drbd"/>
> </rule>
> </rsc_location>
> 
> whats this ?

This is DRBD resource level fencing - it set a location rule preventing r0 from being promoted to master on any node other n1.

You have fencing configured in DRBD config likely in the global_common.conf:

common {
     handlers {
          fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
          after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
     }
     disk {
          fencing resource-only;
     }
}

More here:
http://www.drbd.org/users-guide-8.3/s-pacemaker-fencing.html
or here:
http://www.drbd.org/users-guide/s-pacemaker-fencing.html

HTH

Jake

> 
> thanks
> andreas
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 




More information about the Pacemaker mailing list