VMware Cloud Community
jburen
Expert
Expert
Jump to solution

Precheck failed due to limited disk space

Running precheck on the management cluster gives me this error: Minimal disk space is available in SDDC Manager directory. Available disk space is 2 GB. Recommended disk space is 20.0 GB or more. Clean up unused files from the directory /var/log/vmware.

I know, a very clear error. But solving it is not so simple. At least, not for me.

How can I find the files and/or folders that are using the 60 GB disk space? Can I delete .log.gz files? Or maybe some other files?

 

Consider giving Kudos if you think my response helped you in any way.
Labels (1)
Tags (4)
Reply
0 Kudos
1 Solution

Accepted Solutions
jburen
Expert
Expert
Jump to solution

We checked everything we could check but could not make out why the mount was full. A reboot solved the issue.

Consider giving Kudos if you think my response helped you in any way.

View solution in original post

4 Replies
Lalegre
Virtuoso
Virtuoso
Jump to solution

@jburen,

The .log.gz can always be safely deleted as they are created to ensure the archival of logs in case you need them. In case you identified already that those are the files consuming a lot of space, you can simply delete them.

Reply
0 Kudos
jburen
Expert
Expert
Jump to solution

Even if I delete all .log.gz files the mount seems very full:

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/data_vg-vmware 63G 58G 1.7G 98% /var/log/vmware

But searching for the largest folder with du -a | sort -n -r | head -n 20 gives me the vcf folder which is 360 MB... Where is the other 60 GB?

Consider giving Kudos if you think my response helped you in any way.
Reply
0 Kudos
RajeevVCP4
Expert
Expert
Jump to solution

plz provide out put of this command

df -h; lsblk; lsscsi  ( one line syntax from sddc)

you can also try this KB

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

 

 

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
Reply
0 Kudos
jburen
Expert
Expert
Jump to solution

We checked everything we could check but could not make out why the mount was full. A reboot solved the issue.

Consider giving Kudos if you think my response helped you in any way.