Hello Sandy,
Where are you seeing disks as Thick-provisioned?
C#/Thick Client or Web Client? - Check both.
I am going to assume this cluster is managed by vCenter of a 6.0 build version correlating to the ESXi build of the nodes or higher (if it not then update/upgrade this of course).
You can check the reserved space and ProportionalCapacity of any vSAN Objects via RVC (Ruby vSphere Console) via the vCenter Appliance VM:
Log-in to RVC:
http://www.virten.net/2013/12/getting-started-with-ruby-vsphere-console-rvc/
Navigate to the cluster level e.g. >localhost/DCName/Computers/ClusterName/
Easily check for a high % of Reserved space on the disks (If ALL your Objects are actually Thick then this % Reserved should be near enough the % Used)
>localhost/DCName/Computers/ClusterName> vsan.disks_stats .
If there is a high amount of Reserved % (note that .vswap Objects are Thick by default), run this to print out the specifics of the Objects of all VMs:
localhost/DCName/Computers/ClusterName> vsan.vm_object_info ./ResourcePools/vms/*
If there are Thick-provisioned vmdk-Objects then these should show "(proportionalCapacity = 100)" in the line describing their attributes.
If there are Thick-provisioned Objects that you want to be thin-provisioned then check the Rules of the SP(Storage Policy) that is applied to these Objects/VMs - if the SP has OSR('Object Space Reservation') set to 100 (or anything other than 0) then consider changing this to 0 and re-applying the SP to all Objects/VMs.
If the SP in use DOES have OSR set to 0 AND the Objects/VMs are showing as Thick (from the above checks) AND they are compliant with the SP, then to reconfigure these as thin either:
- Make a new Storage with OSR set to 0 and apply this SP to the Objects/VMs (you can test this with a few VMs at a time to prevent any possible large resync from rebuilding the Objects)
or alternatively (and this *may* cause some sizeable resync if the Objects get rebuilt):
- Edit the current SP (even if it has OSR=0) by adding another parameter with a null value (e.g. IOPS Limit = 0) and then apply this SP to all Objects/VMs with this SP when prompted.
Let us know how you get on, and/or if you don't get any specifics of the above.
Bob
HI,
Please see : https://www.virtuallyghetto.com/2016/06/heads-up-ovfova-always-deployed-as-thick-on-vsan-when-using-... , you may try the power-cli method to convert them . Please as suggested dont choose to deploy Vms thru vsphere thick client , make sure you deploy VMs thru webclient and apply vSAN datastore default policy atleast if you were not using any other customer VM storage policy . Please also make sure object space reservation on your VM-storage-policy set to 0 .