esxcli vsan debug limit get' shows the Free components available on host.# esxcli vsan debug limit get
Component Limit Health: redMax Components: 9000Free Components: 0Disk Free Space Health: greenLowest Free Disk Space: 11 %Used Disk Space: 79649266561191 bytesUsed Disk Space (GB) : 74179.16 GBTotal Disk Space: 138266825195520 bytesTotal Disk Space (GB): 128771.02 GB
VMware vSAN 7.x
VMware vSAN 8.x
When there are too many unassociated objects on vSAN datastore, it would be consuming the components. This would cause the vSAN Cluster to reach its maximum component limit.
Please follow the below KB to list and identify the Unassociated objects:
Procedures for identifying Unassociated vSAN objects
Note: Unassociated does not necessarily mean unused/unneeded. Any vSAN object that is not associated with a registered Virtual Machine will appear as 'Unassociated' when checked via RVC.