/storage/core partition filling up. This occurs due to the generation of numerous core dump files, such as core.netlogond.####, core.updatemgr-worke.###.File system/storage/core is low on storage space. Increase the size of disk /storage/core:Below is the output from vCenter cli:
[ /storage/core ]# df -h /storage/core/Filesystem Size Used Avail Use% Mounted on/dev/mapper/core_vg-core 98G 74G 20G 80% /storage/core
Sample Core files :
[ /storage/core ]# du -sh *16M core.ps.######16M core.ps.######16M core.ps.######16M core.ps.######16M core.ps.######16M core.ps.######175M core.python.######175M core.python.######32G core.updatemgr-worke.#######34G core.updatemgr-worke.#######7.8G core.vpxd-worker.####16K lost+found4.0K netdumps20K software-update4.0K vmware-wcp
This occurs due to the repeated generation of core dump files, commonly named:
core.netlogond.######
core.updatemgr-worker.#####
Other service-related core files
These files are typically created when internal VCSA services crash or encounter fatal errors.
Workaround:
To free up disk space, manually delete core files located in /storage/core using the rm -f command.
For example, [ /storage/core ]# rm -rf core.updatemgr-worke.######
Verify available storage after removing files from core partition:
[ /storage/core ]# df -h /storage/core/Filesystem Size Used Avail Use% Mounted on/dev/mapper/core_vg-core 98G 8.2G 85G 9% /storage/core
Please Note:
1. A full vCenter File based backup and Offline Snapshots of the vCenter is mandatory before we execute the rm -rf command
2. "rm -rf is a destructive command has to be used cautiously and Broadcom is not responsible for any loss of data by incorrectly executing the above mentioned commands.
Below is the KB for reference :
https://knowledge.broadcom.com/external/article/326764