[Pacemaker] Storage Locking To Prevent Split Brain

David Morton david.morton at eroad.co.nz
Wed Oct 24 16:54:18 EDT 2012

Nobody have any words of wisdom gained from years of experience ? I'm
looking at sfex resources configured on a small logical volume in the same
volume group as the main data set at present.

>From the documentation it reads as this is the correct mechanism for the
job ?


On 18 October 2012 08:40, David Morton <davidmorton78 at gmail.com> wrote:

> We're changing our SAN shortly and I'm putting together the procedure /
> config now for the shared storage. This will be based on XFS on top of
> clustered LVM2 via Pacemaker.
> I've implemented the exclusive=yes directive on the LVM resources (volume
> groups) but I am still able to mount on both cluster nodes (2 node cluster)
> in my testing environment. I would have thought that this directive would
> prevent multiple mounting / VG activation given that even when there are no
> cluster comms (this is how i create the split brain, and reboot both nodes)
> the storage is available to both nodes ?
> What is the recommended way of guaranteeing storage exclusiveness in this
> (albeit unlikely) situation where both nodes think they are running by
> themselves ? I've looked at sdb and sfex but have previously been steered
> away from them.
> Dave
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20121025/81a0c563/attachment-0002.html>

More information about the Pacemaker mailing list