Hello jbax
If they are still in reality thick-provisioned (proportionalCapacity = 100) they will not benefit.
I have seen this occur even when it says that the Default vSAN Storage Policy has been applied (and even more times when MARVIN policies are involved).
To start:
Identifying and fixing Thick Objects:
All commands run via RVC at the cluster level:
List disks (so that you can focus on disks with high % RESERVED space, this indicates Objects that are indeed Thick, copy+paste this info for later):
#vsan.disks_stats .
Check policy applied to all VMs:
#spbm.check_compliance ./resourcePool/vms/*
(any Objects that say 'Unknown' here I would be immediately be suspicious of, you can look at their disks via Edit Settings on the VM in the Web Client, click drop-down for the disk in question and it will show you what Storage Policy it is using, if it says 'Datastore Default' this is NOT the same as vSAN Default Storage Policy and I bet will be thick)
Display disk layout for all objects:
#vsan.vm_object_info ./resourcePool/vms/*
(copy-paste into notepad and look for any Objects with "proportionalCapacity = 100", or you can use grep against .txt on a host)
If you have a ton of Objects/disks that have "proportionalCapacity = 100" then create a new Storage Policy identical to the policy they are using (except with a new name), apply this policy to the objects and go back to step one to see if the 'Reserved' space on disks has decreased, if it has then we are on the right track.
Bob
-o- If you found this comment useful or answer please select as 'Answer' and/or click the 'Helpful' button, please ask follow-up questions if you have any -o-