Error: "cannot be inflated because it is not a vmfs thin-provisioned disk" when inflating the vmdk

search cancel

book

calendar_today

VMware vSphere ESXi

Converting a fully utilized thin disk to thick disk when there is no access to the vCenter.
vCenter / Storage vMotion unavailable.
Size of virtual disk shows as full within the datastore.
Disk is thin provisioned.
When attempting to inflate using the ESXi Host UI, the operation fails with the error

cannot be inflated because it is not a vmfs thin-provisioned disk
ESXi - /var/log/hostd.log

2023-05-19T07:56:43.278Z warning hostd[2100372] [Originator@6876 sub=Vdisksvc opID=esxui-b65c-08d3 user=root] The virtual disk (/vmfs/volumes/6177bdb6-17f9f458-83b3-##########/VM/VM.vmdk) cannot be inflated because it is not a vmfs thin-provisioned disk - type: <11>, capacity: <322122547200>, used: <322122547200>.

VMware vSphere ESXi 7.x

This is not a defect or a bug as the code defined is working as expected.

Inflate works on converting thin to thick disk by following the method of eager zero (process to format the disk by writing them with zeros prior to writing any data).
Inflate considers the parameters "capacity" & "space Used" for the VMDK at the time of execution.

Example:
capacity: <322122547200> == spaceUsed: <322122547200>
Inflating the VMDK, with no space left on the virtual disk itself, will fail leading to the error as there is nothing to zero out.

Workaround

You can follow either of the 2 options listed below.

Option 1 - Resize the Virtual Disk

Access the ESXi Host UI.
Right-click the virtual machine.
Click Edit Settings.
Select Virtual Disk.
Increase the size of the disk.

Note: If this option is greyed out, the disk may be running on snapshots or the disk may be at the maximum allowed size depending on the block size of the datastore.

Option 2 - Clone the disk using vmkfstools

thumb_up Yes

thumb_down No