Tinkering with timeouts could be risky, so in case you can't have a second switch - your solution (shutting down all VMs, maintenance, etc) should be the safest. If possible test it on a cluster on VMs, so you get used to the whole procedure. Best Regards,Strahil Nikolov On Wed, Sep 29, 2021 at 16:16, cen<imba...@gmail.com> wrote: On 29. 09. 21 13:31, Vojtech Juranek wrote: > this is possible, but changing sanlock timeouts can be very tricky and can > have unwanted/unexpected consequences, so be very careful. Here is a guideline > how to do it: > > https://github.com/oVirt/vdsm/blob/master/doc/io-timeouts.md
Thank you for your feedback, this seems to be exactly what is happening. After reading the doc, my gut feeling tells me it would be smarter to shut down our VMs, go into maintenance mode and then perform any switch upgrades/reboots instead of trying to tweak the timeouts to survive a possible 3min+ reboot. We don't have any serious uptime requirements so this seems like the easiest and safest way forward. Best regards, cen _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/JEJMMLI2WH72J4PPRKSYHAEQFTIEBPZ5/
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3TYARHX4QMALGVGF7DWUJV7LRC7LVJWP/