[ClusterLabs] Question about fence_mpath

Seth Reid sreid at vendini.com
Fri Apr 28 14:22:11 EDT 2017

So, I'm still not getting fence_mpath working.  This is all on CentOS 7.
> Here's what I did:
> - on each node, put a unique "reservation_key" in /etc/multipath.conf
>   defaults{} section (node1=20170001 and node2=20170002)
> - created the STONITH device on node1 with:
>   pcs stonith create multipath fence_mpath devices=/dev/mapper/
> 36000d310013096000000000000000043 key=20170001 meta provides=unfencing
> It creates, but any time anything tries to fence (manually or by
> rebooting a node), I get errors in /var/log/messages.  Trying to
> manually fence a node gets:
> # pcs stonith fence node2 --off
> Error: unable to fence 'node2'
> Command failed: No such device

I've had a similar problem. Make sure that the /dev/mapper object above
isn't a symlink. In my multiparth.conf, I had added an alias to a device
name, like that, to make it easier, but if I pointed my fencing at that, it
didn't work. However, I could point directly to the object that the symlink
pointed to, and it work. I actually had better luck not even specifying a
device at all. It found the right one.

> Another issue I run into is that fence_mpath tries to access/write to
> /var/run/cluster/mpath.devices, but nothing else creates that directory
> (and it seems that fence_mpath tries to read from it before writing it
> out).
This is because the device isn't "correct". It can read from a symlink, and
it doesn't follow the symlink, so nothing gets written.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170428/1cce3845/attachment-0003.html>

More information about the Users mailing list