`<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 10, 2015 at 10:23 AM, Richard Elling <span dir="ltr"><<a href="mailto:richard.elling@richardelling.com" target="_blank">richard.elling@richardelling.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
</div></div>It is my understanding that ESX doesn't use NFS locking, they implement their own.<br>
This makes sense, because NFSv2/3 locking has been problematic since the beginning,<br>
from all vendors. Again, this is easy to measure.<br></blockquote><div><br></div><div>I thought that too, but looking in the advanced config, there are a couple tunables for nfs locks. NFS.LockRenewMaxFailureNumber, range 1-100, def 3 and NFS.LockUpdateTimeout, range 1-8 default 5. This is on ESXi 5.5.<br><br></div><div>I don't have an non-production datastores connected to ESXi, or else I would test this right away. <br><br></div><div>-Chip<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"> -- richard<br>
<br>
</font></span></blockquote></div><br></div></div>
`