VM provisioning space is high on vSAN after storage vmotion from a non vSAN datastore
search cancel

VM provisioning space is high on vSAN after storage vmotion from a non vSAN datastore

book

Article ID: 397413

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

You have migrated VMs from an NFS datastore to a vSAN datastore and some disks are not converting from Thick provisioned to Thin.

When checking the hard disks on the VM some will show up with the wrong provisioning type. 

Environment

VMware vSAN 7.0.x
VMware vSAN 8.0.x

Cause

After the objects are created on the vSAN storage, some of the objects show "proportionalCapacity" as 100, instead of what was selected in the storage policy. 
This can be verified by running the following command from and ESXI host and looking up the disk
esxcli vsan debug object list --all | less

 

Resolution

Re-apply the storage policy on the VM. This will fix the Object Space Reservation values.

You can also fix from command line using the "Verify storage policy in use" section of the linked KB

Additional Information

You will also see a Skyline health alarm about the thick provisioned disks.