Hi,
NFS hard mounts should not help with sanlock. It should just kill the VMs after 60 seconds same as a soft mount.
The sanlock timeout: I asked RedHat support about that in a case for my RHV environment. They said this should not be changed.
Only thing that came to my mind: disable storage leases in case of planned storage maintenance.
Greetings
Klaas
I know 2 approaches.
1. Use NFS hard mounting option - it will never give error to sanlock and it will be waiting until NFS is recovered (never tries this one, but in theory might work)
2. Change the default sanlock timeout (last time I tried that - it didn't work) . You might need help from Sandro or Sahina for that option.
Best Regards,
Strahil NikolovOn Apr 18, 2019 11:45, klaasdemter@gmail.com wrote:
>
> Hi,
>
> I got a question regarding oVirt and the support of NetApp NFS storage.
> We have a MetroCluster for our virtual machine disks but a HA-Failover
> of that (active IP gets assigned to another node) seems to produce
> outages too long for sanlock to handle - that affects all VMs that have
> storage leases. NetApp says a "worst case" takeover time is 120 seconds.
> That would mean sanlock has already killed all VMs. Is anyone familiar
> with how we could setup oVirt to allow such storage outages? Do I need
> to use another type of storage for my oVirt VMs because that NFS
> implementation is unsuitable for oVirt?
>
>
> Greetings
>
> Klaas
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TSJJKK5UG57CCFYUUCXXM3LYQJW2ODWZ/