Have you considered logs?
You mean /storage/log ?
It's only 100 mb big.
And there was only 1.1 gb in /var/log.
So it's not that too,
Can you provide a screenshot of the VM folder so we can see what files are using the space, e.g. is it the vmdk files or something else.
Is the VM thin or thick provisioned? If thin it will grow over time as you make changes to your VM, install patches etc. The disk will not automatically reclaim space, more info here Reclaim disk space from thin provisioned VMDK f... | HDS Community
Has the memory been increased? This would cause the swap file to increase also.
The link shows commands for ESXi hosts.
My problematic VM is the vcsa VM, not the ESXi VMs.
In Workstations, for all the 12 disks it says "Disk space is not preallocated to this disk". That's thin provisionned.
How to reclaim disk space from the vcsa VM ? (my vcsa is NOT inside an ESX host, it's a separate VM)
So I cannot just ssh into the vcsa and do some commands, since "df -h" shows I'm using almost anything.
I have to clean the vmdk that's in my host Windows machine, but how ?!?
I don't see why it would grow in that manner - other than the snapshot (screenshot shows snapshot file and delta disks ...0001.vmdk but doesn't show sizes). Can it be deleted first of all?
Most space reclamation methods use a tool to zero out unused blocks and then storage vMotion to commit it and shrink the disks but that's not something you can do with workstation unfortunately. All I can think is backing up the DB and redeploying the appliance as a workaround.
My snapshot was already deleted. What you see is from a brand new snapshot.
Why "storage vMotion to commit it" ? Commit what ?
How can I backup the db and import it in the new vcsa deploy ?
could you please post the output of du -h /
above command will give you the details of the files/folder which occupies more space. will help in further isolation.
With "df -h", the size of "/" (dev/sda3) is 5 gb out of 11 gb.
But my vmdk for this disk, with no snapshot, is 8.71 gb out of 12 gb.
There is 3.71 gb lost just there.
Later I'll get back with the output of du -h /
Here it is :
du -h / --max-depth=1
So, the total machine is only 8.9 GB. But the sum of all my vmdks is 32.9 GB.
Which is 24 GB lost. No way at all to get back all this space ?