Here is vmware kb.
Vcenter appliance 6 5 storage core full.
Vmware vcenter 6 7 storage core full.
November 15 2019 recently we have upgraded the vcsa after that noticed some performance issue while loading vcenter inventory.
Stop the vmware services on the vcsa appliance.
4 comments on vmware vcenter server appliance storage log full a while back i was welcomed to the office by a vcenter server appliance critical health alert specifically the storage log filesystem is out of disk space or inodes.
Vmware vcenter server appliance storage log full by gareth lewis in vcenter vcsa vsphere tutorials.
Luckily the fix is rather easy thanks to a blog post by lamw that i found while looking for a solution he mentions in vcsa 6 x you can now expand vmdk s on the fly since the vcsa takes advantage of lvm.
After installing or upgrading an external psc of vcenter server 6 5 the storage core directory is continuously filled to 100.
This repeats every 4 5 hours.
If the security toke service vmware stsd crashes causing the storage core directory to fill up see secure token service vmware stsd in vcenter server 6 7 u1 crashes with core jsvc xxx files causing storage core to fill up.
These can be removed without any issue.
Stop your services delete the core dumps etc.
Vcenter may act sluggish.
Connect to vcenter server appliance console as the root user.
So open the vsphere client web or thick and expand the vmdk see below table for which vmdk to expand.
Vmware vcenter server appliance 5 0 vpxd crashes few seconds after starting to resolve this issue due to core dumps filling the partition.
Storage core partition basically contains the core dumps generated on a event whenever a service crashes within the appliance.
Logging into the vcsa via ssh and running df h showed that the storage core area was indeed 100 utilized.
You can drill down into your storage core directory and issue the command for looking at file sizes.
I saw 2 core dumps in particular that were taking up all the drive space.