<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 4, 2016 at 7:03 PM, Michal Skrivanek <span dir="ltr"><<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 4 Oct 2016, at 09:51, Gary Lloyd <<a href="mailto:g.lloyd@keele.ac.uk">g.lloyd@keele.ac.uk</a>> wrote:<br>
><br>
> Hi<br>
><br>
> We have Ovirt 3.65 with a Dell Equallogic SAN and we use Direct Luns for all our VMs.<br>
> At the weekend during early hours an Equallogic controller failed over to its standby on one of our arrays and this caused about 20 of our VMs to be paused due to IO problems.<br>
><br>
> I have also noticed that this happens during Equallogic firmware upgrades since we moved onto Ovirt 3.65.<br>
><br>
> As recommended by Dell disk timeouts within the VMs are set to 60 seconds when they are hosted on an EqualLogic SAN.<br>
><br>
> Is there any other timeout value that we can configure in vdsm.conf to stop VMs from getting paused when a controller fails over ?<br>
<br>
</span>not really. but things are not so different when you look at it from the guest perspective. If the intention is to hide the fact that there is a problem and the guest should just see a delay (instead of dealing with error) then pausing and unpausing is the right behavior. From guest point of view this is just a delay it sees.<br>
<span class=""><br>
><br>
> Also is there anything that we can tweak to automatically unpause the VMs once connectivity with the arrays is re-established ?<br>
<br>
</span>that should happen when the storage domain monitoring detects error and then reactivate(<a href="http://gerrit.ovirt.org/16244" rel="noreferrer" target="_blank">http://gerrit.<wbr>ovirt.org/16244</a>). It may be that since you have direct luns it’s not working with those….dunno, storage people should chime in I guess...<br></blockquote><div><br></div><div><br></div><div>We don't monitor direct luns, only storage domains, so we do not support</div><div>resuming vms using direct luns.</div><div><br></div><div>multipath does monitor all devices, so we could monitor the devices status</div><div>via multipath, and resume paused vms when a device move from faulty</div><div>state to active state.</div><div><br></div><div>Maybe open an RFE for this?</div><div><br></div><div>Nir</div></div></div></div>