Top ESX/ESXi Known Issues/Workarounds/Best Practices for NFSv3
- Last Updated:
- VMware ESXi 5.5 U1
- ESXi 5.x host
The following are the top known issues, workarounds, and best practices for ESX/ESXi NFS clients when used with NetApp FAS controllers running Data ONTAP 7-Mode or clustered Data ONTAP:
Known Issues and Workarounds:
- Intermittent NFS APDs on the VMware ESXi 5.5 U1
When running the ESXi 5.5 Update 1, the ESXi host intermittently loses connectivity to NFS storage and an All Paths Down (APD) condition to NFS volumes is observed.
This issue is resolved in ESXi 5.5 Express Patch 04. For instructions to install the patch, see VMware articles 2076392 and 2077414.
Note: The fix is a part of ESXi 5.5 U2 and later releases, no additional patches required.
- Random disconnection of NFS exports under workloads with excessive number of requests
On some NetApp storage controllers with NFS enabled, you might experience the following symptoms:
- The NFS datastores appear to be unavailable (greyed out) in vCenter Server, or when accessed through the vSphere Client.
- The NFS shares disappear and reappear again after a few minutes.
- Virtual machines located on the NFS datastore are in a hung/paused state when the NFS datastore is unavailable.
This issue is most often seen after a host upgrade to ESXi 5.x or the addition of an ESXi 5.x host to the environment.
For more information about this issue, see BUG 654196.
- vSphere 2015 VMware Virtual Volumes(VVOL): I/O disruption on Windows 2012 Guest Operating System during non-negotiated Storage failover operations
During a non-negotiated Storage failover operations in a VVOL environment you might experience random I/O disruptions on Windows 2012 Guest Operating System. This issue is being investigated and users are advised to exercise caution while performing non- negotiated Storage failover operations.