I think its not related to something on the trueNAS side. if you are using iscsi multipath you should be using round-robin , if one of the paths goes down you still have the other path with your information., so no sanlock . unfortunately if you want iscsi mpath on ovirt, its prefered to edit the config by hand and test. also, with multipath, you can tell the os to 'stop using' one of the paths( represented as a disk).
 so, for example:
multipath -ll should* be looking like this:
36589cfc000000341111968eacf965e3c dm-17 FreeNAS ,iSCSI Disk     
size=50G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=0 status=enabled
  |- 31:0:0:5  sdl 8:176 failed faulty running
  |- 32:0:0:5  sdm 8:192 failed faulty running
  |- 35:0:0:5  sdo 8:224 failed faulty running
  `- 34:0:0:5  sdn 8:208 failed faulty running

and working correctly like this:
36589cfc000000ee205ed6757fa724bac dm-2 FreeNAS ,iSCSI Disk     
size=5.5T features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 13:0:0:10 sdi 8:128 active ready  running
  |- 15:0:0:10 sdk 8:160 active ready  running
  |- 28:0:0:10 sdg 8:96  active ready  running
  `- 29:0:0:10 sdj 8:144 active ready  running
(yes, they are different ones, I wont disconnect one path just to show an example =) )

hope I clarified a bit.

cant tell how it would work on nfs or if it works at all.


2017-06-06 10:06 GMT-03:00 Chris Adams <cma@cmadams.net>:
Once upon a time, Sven Achtelik <Sven.Achtelik@eps.aero> said:
> I was failing over by rebooting one of the TrueNas nodes and this took some time for the other node to take over. I was thinking about asking the TN guys if there is a command or procedure to speed up the failover.

That's the way TrueNAS failover works; there is no "graceful" failover,
you just reboot the active node.

--
Chris Adams <cma@cmadams.net>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users