VMware ESXi and vSphere Cluster Management

Convert a Thin-Provisioned Virtual Disk to Thick Provisioning in VMware ESXi

Learn how to inflate a thin-provisioned VMDK into a fully allocated thick disk using the vSphere web client, including planning, validation, and troubleshooting.

Inflating a virtual disk converts an existing thin-provisioned VMDK into a fully allocated thick disk. The operation does not increase the disk's configured size and does not expand partitions or files inside the guest operating system.

Thin and thick virtual disk provisioning

A VMDK is VMware's virtual disk file format. A virtual machine uses the VMDK as its virtual hard disk, while the files that make up the VMDK are stored in a VMware datastore. A datastore is storage presented to ESXi for virtual machine files and virtual disks.

Thin provisioning allocates physical datastore blocks as the virtual disk uses them. A thin disk can have a large configured capacity while initially consuming much less physical space.

Thick provisioning allocates the disk's complete configured capacity on the datastore. The space is reserved even if the guest operating system has not yet written data to every part of the disk.

Provisioning format affects datastore allocation and may affect performance, depending on the storage type and workload. It does not change the capacity presented to the guest operating system.

What inflating a VMDK does

Inflate is the vSphere operation that fully allocates a thin-provisioned virtual disk without increasing its configured size. ESXi allocates the previously unallocated blocks until datastore consumption approaches the VMDK's configured capacity.

For example, a 10 GB thin disk consuming about 3 GB may consume close to 10 GB after inflation. The guest still sees a 10 GB disk before and after the operation.

• Inflation changes datastore allocation from thin to fully allocated thick storage.
• Inflation does not extend the VMDK.
• Inflation does not resize a partition or filesystem.
• Inflation does not add guest files or otherwise expand the guest operating system.

Extending a virtual disk is a different task. Extension increases the VMDK's configured capacity; the guest operating system may then require a separate partition or filesystem expansion.

Plan the conversion

Required preconditions

• Power off the target virtual machine completely. Do not begin while it is running, suspended, or in another active power state.
• Use an account with permissions to browse the datastore and perform the required virtual machine and disk operations. See Assign Permissions if permission roles need review.
• Identify the datastore that contains the VM files.
• Identify the correct VMDK descriptor file, especially when the VM has multiple disks.
• Review active snapshots and the VM's file layout before changing a disk format.

Calculate the required free space

Estimate the additional datastore capacity with this calculation:

Estimated additional capacity = configured disk capacity - current datastore consumption

For a 100 GB thin disk consuming 35 GB, plan for approximately 65 GB of additional space. Leave a safety margin for VM files, datastore overhead, other virtual machines, snapshots, and background operations.

Check both the VM's configured disk size and the datastore's current free space. Do not assume that a datastore with enough space for the configured disk has enough space for the conversion; only the unallocated portion needs to be added, but other activity can reduce available capacity during the task.

Inflate the VMDK in the vSphere web client

1. Power off the target virtual machine.
2. Open the relevant datastore from the vSphere inventory. The datastore is the storage location containing the VM's files.
3. Launch the datastore browser, the vSphere interface for inspecting and managing datastore files.
4. Open the folder for the target virtual machine.
5. Locate the intended virtual disk descriptor file with the .vmdk extension. Match its filename and configured capacity with the disk shown in the VM's hardware settings.
6. Do not select snapshot-related files or an unfamiliar disk merely because its name appears similar.
7. Select the correct VMDK and choose the datastore browser's Inflate disk action. The exact menu placement can vary by vSphere version and permissions.
8. Confirm the operation if prompted.
9. Monitor Recent Tasks or the task panel until the inflation task completes successfully. Do not power on the VM while the operation is still running.
10. Return to the VM configuration or datastore view and verify the result before starting the VM.

Validate the conversion

1. Confirm that the inflation task completed successfully rather than merely being submitted.
2. Compare datastore free space before and after the operation. Consumption for the selected VMDK should now be close to its configured capacity, subject to VM file and datastore overhead.
3. Check the disk's provisioning type in the VM configuration or datastore interface if that information is exposed. It should no longer be reported as thin.
4. Verify that the VMDK's configured size has not changed. Inflation should not increase it.
5. Power on the virtual machine after successful completion.
6. Confirm that the guest operating system starts normally and that its disk reports the same capacity as before.
7. Verify that files, partitions, and filesystems inside the guest are unchanged. No guest expansion occurs merely because the VMDK was inflated.

Operational cautions

• Review snapshots before making storage-format changes. Snapshot files can make the VM's disk layout harder to interpret and can consume additional datastore space.
• In a multi-disk VM, distinguish the operating-system disk from data disks by comparing filenames and capacities with the VM hardware settings.
• A VMDK descriptor is not necessarily the only file associated with a virtual disk. Use the datastore browser's displayed file information and the VM configuration rather than selecting files by name alone.
• Do not select snapshot-related VMDKs unless the intended operation explicitly concerns that disk chain and the layout has been reviewed.
• Inflation does not provide additional guest capacity. Use a separate disk-extension procedure when the requirement is to increase the guest-visible disk size.

Troubleshooting

The Inflate action is unavailable

• Confirm that the VM is powered off.
• Confirm that the selected item is the eligible virtual disk descriptor with a .vmdk extension.
• Review the disk's provisioning format; an already thick-provisioned disk has nothing to inflate.
• Verify that the account has the required datastore browsing and disk-operation permissions.

The datastore does not have enough space

The datastore may lack capacity for the unallocated portion of the thin disk, or another VM, snapshot, or background task may be consuming space.

• Free capacity before retrying.
• Move the VM or disk to a datastore with sufficient capacity.
• Include a safety margin instead of allocating only the exact calculated difference.

The wrong disk may have been selected

Similar filenames and snapshot-related files can cause mistakes. Power off the VM, compare each disk's filename and configured capacity with the VM hardware settings, and review the snapshot state before taking action.

The disk appears unchanged after the task

• Check Recent Tasks and wait for the operation to finish.
• Check datastore free-space values rather than only the disk's configured capacity.
• Confirm that the selected disk was not already fully allocated.
• Refresh the datastore browser or VM configuration view if it is showing stale information.

Exam-relevant points

• Thin provisioning consumes datastore space as blocks are used; thick provisioning allocates the full configured capacity.
• Inflating a VMDK changes allocation format, not configured disk size.
• The guest-visible capacity remains unchanged after inflation.
• The VM should be powered off before using the datastore browser's Inflate action.
• Before inflation, calculate the unallocated portion and confirm sufficient datastore capacity with a safety margin.

For broader ESXi administration practice, review the VMware ESXi online course, basic ESXi configuration, and datastore concepts in vSAN.