VMware vSAN 7.0.x ESA
VMware vSAN 8.0.x ESA
This was a new ESA cluster and initially disks were added that were not ESA compatible. Disks were removed and replaced but the configstore still retained information of the removed disks. Leading to vsan capacity reporting twice the available capacity.
To resolve the issue user should:
1. Identify all disks currently tracked in the configstore: configstorecli config current get -c vsan -g system -k host_config
2. Compare this list against the active storage pool: esxcli vsan storagepool list
3. Remove the stale UUIDs: esxcli vsan storagepool remove -u <UUID>
4. Run configstorecli command again to verify the disk entry is indeed removed: configstorecli config current get -c vsan -g system -k host_config
The total license capacity usage should now reflect accurately the total physical disk capacity.