Deploy Template, Clone, Storage vMotion, and snapshot consolidation operations are failing for virtual machines running on NFS volumes.
Article ID: 426126
Updated On:
Products
Issue/Introduction
Deploy Template, Clone, svMotion and snapshot consolidation tasks do not work for virtual machines or templates running on NFS volumes.
Below error is seen in UI during the a Storage vMotion task :
Error caused by file /vmfs/volumes/2cafc019-#########/Sample-virtual-machine/Sample-virtual-machine.vmdk
Copying Virtual Machine files
Below error is seen in UI during Consolidation :
An error occurred while consolidating disks: Unknown error.
Hostd.log:
<YYYY-MM-DD><time> verbose hostd[2100003] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/2cafc019-########/Sample-virtual-machine/Sample-virtual-machine.vmx opID=mh1otv93-5244704-auto-34eue-h5:70888097-3e-01-6b-ac2c] Incomplete layout due to descriptor file /vmfs/volumes/2cafc019-########/Sample-virtual-machine/Sample-virtual-machine-000004.vmdk not found in extent map
<YYYY-MM-DD><time> verbose hostd[2100003] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/2cafc019-########/Sample-virtual-machine/Sample-virtual-machine.vmx opID=mh1otv93-5244704-auto-34eue-h5:70888097-3e-01-6b-ac2c] Incomplete layout due to descriptor file /vmfs/volumes/2cafc019-########/Sample-virtual-machine/Sample-virtual-machine-000005.vmdk not found in extent map
<YYYY-MM-DD><time> verbose hostd[2100003] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/2cafc019-########/Sample-virtual-machine/Sample-virtual-machine.vmx opID=mh1otv93-5244704-auto-34eue-h5:70888097-3e-01-6b-ac2c] Incomplete layout due to descriptor file /vmfs/volumes/2cafc019-########/Sample-virtual-machine/Sample-virtual-machine-000006.vmdk not found in extent map
Syslog.log:
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: vendor_nas_plugin: SUCCESSES: RsrvSpace [0] Cln-Full [0] Cln-Lazy [0] cln-DRun [0], Ext-stats [440]
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: vendor_nas_plugin: FAILURES: RsrvSpace [0] Cln-Full [0] Cln-Lazy [0] cln-DRun [0], Ext-stats [17018]
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: NAS Mapping Used successfully for 18260 times
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: vendor_nas_plugin: SUCCESSES: RsrvSpace [0] Cln-Full [0] Cln-Lazy [0] cln-DRun [0], Ext-stats [448]
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: vendor_nas_plugin: FAILURES: RsrvSpace [0] Cln-Full [0] Cln-Lazy [0] cln-DRun [0], Ext-stats [19748]
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: NAS Mapping Used successfully for 20998 times
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: vendor_nas_plugin: SUCCESSES: RsrvSpace [0] Cln-Full [0] Cln-Lazy [0] cln-DRun [0], Ext-stats [456]
<YYYY-MM-DD><time> vaainasd[2098940]: VAAI-NAS :: vendor_nas_plugin: FAILURES: RsrvSpace [0] Cln-Full [0] Cln-Lazy [0] cln-DRun [0], Ext-stats [20051]
<YYYY-MM-DD><time> Er(11) vaainasd[2098667]: DISKLIB-PLUGIN : :[vendor_nas_plugin : /vmfs/volumes/2cafc019-#########] : Extended stats failed:[/vmfs/volumes/2cafc019-#########/Sample-virtual-machine/Sample-virtual-machine.vmdk], Error: Unknown error.
<YYYY-MM-DD><time> Er(11) vaainasd[2098667]: DISKLIB-PLUGIN :: Skip priting per plugin stat summary, time gap between last print cycle and current is less than :3600 sec.
Environment
- ESXi 8.x
- Storage protocol : NFS
- NetAppNasPlugin : 2.0.1-16
Cause
The NetAppNasPlugin for VAAI is in use and is failing to fetch the data.
Resolution
This is a 3rd-party issue and should be further investigated by NetApp array vendor.
Temporary Workaround: Stop the vaai-nasd service and/or remove the NetAppNasPlugin VIB from the ESXi host and retry the operation(s).
Confirm the plugin version on the affected host using: esxcli software vib list | grep NetAppStop the VAAI NAS daemon to bypass hardware acceleration: /etc/init.d/vaai-nasd stopRetry the clone or deployment operation.
Remove the problematic VIB if the workaround is successful: esxcli software vib remove -n NetAppNasPlugin
Possible Permanent Resolution: Working with NetApp, change the array configuration parameters for the NFS protocol on the NetApp NAS.
Note: Changing the NAS protocol from nfs3 to just nfs may resolve the error. We recommend reviewing the following article with NetApp and evaluating whether the configuration applies to your environment: Configure export policies for ONTAP to allow VAAI over NFS
Additional Information
Feedback
