[Pacemaker] Problems with SBD fencing

Lars Marowsky-Bree lmb at suse.com
Wed Aug 21 10:27:39 EDT 2013


On 2013-08-20T08:52:00, "Angel L. Mateo" <amateo at um.es> wrote:

Sorry, I was on vacation for a few weeks, thus only chiming in now.

Instead of the Linux-HA Wiki page, please look here for the
documentation: https://github.com/l-mb/sbd/blob/master/man/sbd.8.pod

(Or, on a system with sbd installed, simply type "man sbd")

The most common problems for fencing failures with SBD:

- Pacemaker's stonith-timeout is not long enough to account for sbd's
  msgwait. It needs to be at least 50% larger. (Pacemaker uses some of
  the stonith-timeout for the look-up phase, and it isn't available for
  the actual fence request.)

- The storage is not truly shared.

  Then the node can't actually "see" the other, and will not be able to
  find the messaging slot. Hence, fencing will fail.

> 	For me to work (ubuntu 12.04) I had to create /etc/sysconfig/sbd file with:
> 
> SBD_DEVICE="/dev/disk/by-id/wwn-0x6006016009702500a4227a04c6b0e211-part1"
> SBD_OPTS="-W"
> 
> 	and the resource configuration is
> 
> primitive stonith_sbd stonith:external/sbd \
>         params
> sbd_device="/dev/disk/by-id/wwn-0x6006016009702500a4227a04c6b0e211-part1" \
>         meta target-role="Started"

In the newer versions, it is not necessary to have the "params" on the
primitive anymore - it'll read the /etc/sysconfig/sbd file. Overriding
that shouldn't be really necessary.

I can assure you that sbd fencing is working fine in SLE HA 11 SP3, or
my lab cluster would never complete a single fence successfully ;-)


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde





More information about the Pacemaker mailing list