<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br></div><div><br></div></div></div></div>
<br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So, I'm still not getting fence_mpath working. This is all on CentOS 7.<br>
Here's what I did:<br>
<br>
- on each node, put a unique "reservation_key" in /etc/multipath.conf<br>
defaults{} section (node1=20170001 and node2=20170002)<br>
<br>
- created the STONITH device on node1 with:<br>
pcs stonith create multipath fence_mpath devices=/dev/mapper/<wbr>36000d310013096000000000000000<wbr>043 key=20170001 meta provides=unfencing<br>
<br>
It creates, but any time anything tries to fence (manually or by<br>
rebooting a node), I get errors in /var/log/messages. Trying to<br>
manually fence a node gets:<br>
<br>
# pcs stonith fence node2 --off<br>
Error: unable to fence 'node2'<br>
Command failed: No such device<br></blockquote><div><br></div><div>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.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Another issue I run into is that fence_mpath tries to access/write to<br>
/var/run/cluster/mpath.<wbr>devices, but nothing else creates that directory<br>
(and it seems that fence_mpath tries to read from it before writing it<br>
out).<br>
<br></blockquote><div><br></div><div>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.</div><div><br></div><div> </div></div><br></div></div>