VMware vSAN 7.x
VMware vSAN 8.x
This could be due to Missing or Unassociated objects present in the cluster which can still be contributing to the used space in the vSAN cluster.
To verify the Missing objects:
esxcli vsan debug object list --all | grep -i "path|object uuid"Object UUID: #######-####-####-####-#######Size: 255.00 GBType: vdfsPath: /vmfs/volumes/vsan:#############################/#############.vmdk (Missing)To remove the unwanted objects from the vSAN cluster, open a ticket with Broadcom support to assist further.