vCenter server upgraded/deployed using thick provisioned disks, Extra-Large deployment on vSAN, need to convert to thin provisioning per vSAN storage policy to reclaim space.
VMware vSAN (all versions)
Symptoms
- vCenter was deployed to a vSAN Custer using "Thick Provision lazy Zero" disks during configuration. This deployment along with the vSAN default policy in use will allocate 100% of space to disk.
- vSAN objects OSR attribute is set to thick for affected VM
# esxcli vsan debug object list --vm-name=vm1
Policy:
stripeWidth: 1
cacheReservation: 0
proportionalCapacity: 100 <<< Object space reservation attribute is thick
hostFailuresToTolerate: 1
forceProvisioning: 0
spbmProfileId: aa6d5a82-1c88-45da-85d3-############
spbmProfileGenerationNumber: 0
CSN: 1007
spbmProfileName: vSAN Default Storage Policy
Used:
63753420800 <<< 63 GB usage
Size:
1535450808320 <<< 1.5 TB provisioned space
Type:
vdisk
Path:
/vmfs/volumes/vsan:52f4da6bda089860-eaf5############/f3ea5b68-f003-afd9-13ed-############/vm1.vmdk (Exists)
Convert the vCenter disks to thin provisioning using the below steps.
To apply the same policy to all disks: Select the desired policy from the dropdown list and click "Apply to All".
To configure policies for individual disks: Select the "Configure per disk" option and choose a different policy for each virtual disk.
4. Apply the changes:
In vCenter web-client VM should now report as thin provisioned and the correct used space vs provisioned space per the vSAN policy in use. If the VM is reporting the same used space and provisioned space in vCenter, vMotion the VM to a new host to have it report correctly.