Error | Cause of the Error | Resolution |
msg.disklib.NOSPACE | This issue occurs if the datastore on which the virtual disk resides does not have enough free space to accommodate the increase in the virtual machine size. |
To resolve this issue, either create more free space in the datastore by migrating or deleting unnecessary virtual machines and files, or increase the size of the datastore.
If the datastore is a VMFS volume, see Troubleshooting a datastore or VMFS volume that is full or near capacity (1003412).
|
msg.fileio.lock | This issue occurs if the virtual disk is already actively in use and locked by some ESXi host. In certain circumstances, these locks may not be released when the virtual machine is powered off. |
To prevent concurrent changes to critical virtual machine files and file systems, ESXi/ESX hosts establish locks on these files including the virtual disks.
To resolve this issue, see Investigating virtual machine file locks on ESXi (10051). |
msg.disklib.UNSUPPORTEDFEATURE | This issue occurs if the ParentCID parameter in the virtual disk's descriptor file is not set to ffffffff. | To resolve this issue, see Extending a virtual disk fails with the error:msg.disklib.UNSUPPORTEDFEATURE (2109730). |
msg.disklib.INVAL or 22 (Invalid argument) |
This issue occurs if an invalid argument was passed for extend operation. This can happen because of various reasons:
|
If the cause of your failure is not listed here, file a support request. For more information on how to file a support request, see How to file a Support Request in Customer Connect (2006985). |
5 (Input/output error) | This issue occurs if ESXi host has a problem accessing the underlying storage device or datastore. |
Troubleshoot and resolve any issues with the underlying storage device:
|
12 (Cannot allocate memory) |
This issue occurs if any of the software component in the ESXi storage stack, such as VMFS module, runs out of heap memory capacity.
Another instance where this can occur is if there are lot of stale snapshot files in the data store on which the virtual machine is located.
|
If the issue is due to VMFS heap exhaustion, see ESXi/ESX host reports VMFS heap warnings when hosting virtual machines that collectively use 4 TB or 20 TB of virtual disk storage (1004424).
If the issue is due to stale snapshot files, see Committing snapshots when there are no snapshot entries in the Snapshot Manager (1002310). If the issue is due to other reasons, file a support request. For more information, see How to file a Support Request in Customer Connect (2006985). |