vCenter server low disk space.
To Fix the issue by expanding the corresponding VMDK of vCenter, please follow these steps:
This issue could prevent you from being able to log into vCenter at all.
- Log into vCSA via SSH.
- List the partitions by running the following command: df –h
- You will be able to see the affected partition/disk as shown below.
- Look up the corresponding VMDK file from the following table:
| DISK (VMDK) | DEFAULT SIZE (TINY VCSA) |
MOUNT POINT | PURPOSE |
| VMDK1 | 12GB | / (10GB) /boot (132MB) SWAP (1GB) |
Boot directory where the kernel images and boot load configurations go |
| VMDK2 | 1.3GB | /tmp | Temporary directory used to store temporary files generated or used by services from vCenter Server |
| VMDK3 | 25GB | SWAP | Swap directory used when the system is out of memory to swap to disk |
| VMDK4 | 25GB | /storage/core | Core directory where core dumps from VPXD process from the vCenter Server are stored, |
| VMDK5 | 10GB | /storage/log | Log directory where vCenter Server stores all logs for the environment |
| VMDK6 | 10GB | /storage/db | VMware Postgres database storage location |
| VMDK7 | 5GB | /storage/dblog | VMware Postgres database logging location |
| VMDK8 | 10GB | /storage/seat | Stats, Events and Tasks (SEAT) directory for VMware Postgres |
| VMDK9 | 1GB | /storage/netdump | VMware Netdump collector repository that stores ESXi dumps |
| VMDK10 | 10GB | /storage/autodeploy | VMware Auto Deploy repository that stores the thinpackages used for stateless booting of ESXi hosts. |
| VMDK11 | 5GB | /storage/invsvc | VMware Inventory Service directory where the xDB, Inventory Service bootstrap configuration file, and tomcat configuration files reside. |
- In our example, the corresponding VMDK is VMDK5.
- Edit the VCSA VM configuration and extend the VMDK to a desired size.
- Now, expand the partition from within the VCSA by running the following commands:
shell.set –enabled true
vpxd_servicecfg storage lvm autogrow
or just reboot VCSA.
Disk expansion is much easier than deleting the content data.
- Now, run df-h again and see that the size has changed.
And also the health status of VCSA has changed to “Good”.
Some of the information in this post were copied from another blog.
Thank you,