vcenter-appliance-vcsa-root-partition-full

What a mess! VCSA cannot be updated anymore or is stuck because of a full root Partition.

Luckily there are straightforward procedures to investigate what files are filling the root partition and how to get rid of them.

Typical symptoms?

  • ISO staging of the update fails
  • vCSA update fails at step #/#
  • some vCSA services cannot be started

Filesystem check

Log into your VCSA console, enable the shell and open the shell.

shell.set –enabled true
shell
df -h

VCSA root partition full

Ignore the Use % number in the screenshot above, as the partition has been cleaned up already. But any number higher than 95% will stop your update procedure.

When using Performance Analyzer we have a special Highlights dashboard for VM partitions, that can be used to check the partition utilization as well.

Performance Analyzer / check vCSA partition

Please download the dashboard here, to import it into Performance Analyzer: DownloadMore information at http://manual.opvizor.com

How to resize the partition

If you don’t want to make your hands dirty and clean up the partition, you can resize the related virtual disk and partition by following this KB article: 

https://kb.vmware.com/s/article/2126276

The big issue here is, that you just postpone the file cleanup until the partition fills up again.

How to clean up the partition

audit.log

In case the audit.log is filling the partition, the task is quite simple and described in the following KB article: 

https://kb.vmware.com/s/article/2149278

  1. cd /var/log/audit
  2. ls -lh
  3. rm -rf audit.log

Check the KB article for all steps to make sure the audit.log is not filling up again.

mqueue

Another possible reason for a filled up partition are files in /var/spool/mqueue – a less documented situation.

In general, you can use the following command to find the largest directories checking the current and the first subdirectory: df -h -d1

  1. df -h -d1 /var
  2. if it’s /var/log that is very big, check the audit.log solution
  3. if it’s /var/spool, continue here
  4. find /var/spool/mqueue -name "*" -delete

The reason to use find and delete instead of rm is, that most of the time /var/spool/mqueue contains to many files to be handled by rm.

Check the partitions again using df -h and restart the appliance if needed.

Btw. You should consider creating a snapshot before deleting any files

RELATED ARTICLES

Save energy without reducing VM performance in your VMware vSphere cluster
16 August 2022
Over the last couple of decades energy consumption went up massively in every data center and while the…
Dennis
Metrics & Logs support for IoT - Bringing Secure Monitoring and Logging to the Edge
7 July 2022
Simple uptime monitoring for Internet-of-Things (IoT) is well-known and requires knowing if the devices are up and running.…
Dennis
Monitoring Azure SQL Managed Instance with Opvizor Metrics & Logs
17 January 2022
When you have critical applications and business processes that rely on Azure resources, it's critical to keep an…
Dennis

White Paper — Registration

You will receive the research paper by mail.

Codenotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on Codenotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.

Subscribe to our newsletter