<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 28, 2017 at 11:25 AM, Chris Adams <span dir="ltr"><<a href="mailto:linux@cmadams.net" target="_blank">linux@cmadams.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>Once upon a time, Seth Reid <<a href="mailto:sreid@vendini.com" target="_blank">sreid@vendini.com</a>> said:<br>
</span><span>> I've had a similar problem. Make sure that the /dev/mapper object above<br>
> isn't a symlink. In my multiparth.conf, I had added an alias to a device<br>
> name, like that, to make it easier, but if I pointed my fencing at that, it<br>
> didn't work. However, I could point directly to the object that the symlink<br>
> pointed to, and it work. I actually had better luck not even specifying a<br>
> device at all. It found the right one.<br>
<br>
</span>But the multipath devices are always symlinks - how do you access it?<br>
The only "real" devices are /dev/dm-<number>, but those names are not<br>
stable, so you can't use those for anything.</blockquote><div><br></div><div>This confused me too when I set up my cluster. I found that everything worked better if I didn't specify a device path. I think there was documentation on Redhat that led me to try removing the "device" options.</div><div><br></div><div>Also thinking back, I'm using fence_scsi, but in a multipath environment. Fence_scsi detected the shared device and everything worked very very smoothly for me. I apologize for not realizing that I had used fence_scsi (and not fence_mpath), but give it a shot removing the "device" options from your stonith command.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote></div></div></div>