VSAN

[ANANDA_M]

We recently encountered an error in our vSAN Cluster (TEST), indicating that after one additional host failure, the vSAN Cluster may not have sufficient resources to rebuild all objects. However, in this cluster, no host is in maintenance mode.

Currently, our vSAN capacity stands at 80 TB, with only 28 TB of free space available. Additionally, we have approximately 6 TB of total running VM VMDK data within the cluster.

So, my concern is how to fix this issue and clear out the unwanted jumbi files.

[TheBobkin]

@ANANDA_M, note that that that health check being triggered (https://kb.vmware.com/s/article/2108743) isn't an "error" - it is an informational alert informing you what the clusters storage utilisation and data-repair state would be if a node were to fail and be unfixable for a prolonged period.

Note that any VMs that are unregistered from vSphere inventory but not deleted still consume space on vsanDatastore - you should start by checking are there any/many large VMs that are not registered in inventory, are no longer needed and can be removed.
Another low-hanging fruit for freeing space can be unconsolidated snapshots which have grown to large size from being left on running VMs for a prolonged period, these should be consolidated ('esxcli vsan debug object list --all' output is useful for identifying these).

Other than these, you should look at what unassociated objects you have in this cluster, but obviously only remove any that you are 100% sure are no longer needed (https://kb.vmware.com/s/article/70726)