Support > Knowledge Base
Knowledge Base
Search the Knowledge Base: |
Search the Knowledge Base: |
Ensuring the VMkernel parameter NFS.LockDisable is set to default
Purpose
This article discusses the advanced VMkernel parameter NFS.LockDisable and provides information about its recommended setting.
Resolution
NFS.LockDisable has a default value of 0. This value enforces locking on the NFS datastore.
Only the default value is supported. VMware strongly recommends that you do not change the value to 1 to disable locking.
Changing the value from the default in VirtualCenter, for any ESX host, can lead to possible corruption of files stored on NFS storage used by ESX. The NFS.LockDisable setting must remain at the default value of 0.
When NFS.LockDisable is set to 1, all virtual machines powered on or VMotioned to this host do not have the associated .lck files. In the case of a High Availability (HA) event triggered by an isolation response, virtual machines are powered up on a second host while the original virtual machines continue to run.
If the NFS.LockDisable is set to 1, you must change it back to 0 on all hosts.
To change the setting back to 0:
- Perform a complete shut down of the virtual machine. When the virtual machine is powered on, the .lck file is created.
OR
- VMotion the virtual machine to an ESX host that has NFS.LockDisable set to 0.
The .lck files are hidden files and cannot be seen from the VMware Infrastructure Client datastore browser. To show the hidden files to verify that the setting took effect:
- Log in to the ESX host using an SSH client.
- Change into the directory that contains the virtual machine.
- Run the command:
ls -a
Feedback
Actions
- KB Article: 1006129
- Updated: Aug 14, 2009
- Products:
VMware ESX - Product Versions:
VMware ESX 3.0.x
VMware ESX 3.5.x
VMware ESXi 3.5.x Embedded
VMware ESXi 3.5.x Installable