There has been a lot of discussion(check Scott’s take on this) around this advanced NFS setting called “NFS.LockDisable”. In short, you can disable the locking mechanism on NFS volumes with this setting.
In the past NetApp had a best practices document which stated that it should be disabled by setting it to “1”. But, as some noticed this can and probably will result in corrupt file-systems. So this “best practice” mysteriously disappeared from the NetApp VI3 Best Practices guide and a KB Article with the VMware best practice on this setting popped up.
So if you did set “NFS.LockDisable” to 1 please change it back to “0”.
It might be beneficial to also implement the “prefvmx.ConsolidateDeleteNFSLocks” that Scott discussed along with patch ESX350-200808401-BG. This setting is to avoid long delays when deleting ESX snapshots. This can take up to 30 seconds, which is quite long compared to iSCSI or FC. So you should only implement this fix if you run NFS and do VMware snapshots at them same time and are experiencing these dalays.
I do recommend that everyone with an NFS filer takes a look at the NetApp best practices document because it does contain valuable information, but before you apply it besure that it doesn’t conflict with a VMware best practice!