VMware Cloud Community
andvm
Hot Shot
Hot Shot
Jump to solution

storage log almost full and VCSA on vSAN

File system /storage/log is low on storage space. Increase the size of disk /storage/log  - Should I increase the related vdisk size or delete any logs?

on another note - do you see any issues if I migrate (storage vmotion) the VCSA to vSAN? (do not think there is any reason why it is not recommended right?)

Thanks

 

Reply
0 Kudos
1 Solution

Accepted Solutions
Ajay1988
Expert
Expert
Jump to solution

Yes. They seem okay to delete

In ur case ; Investigate /storage/log/vmware/eam .
cd to /storage/log/vmware/eam and run du -shc * to check the culprit.

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ

View solution in original post

Tags (1)
Reply
0 Kudos
11 Replies
Ajay1988
Expert
Expert
Jump to solution

Try to find what is taking space on /storage/log  . The below will help 
du -shc *
du -skhxc /storage/log/vmware/* | sort -n

I don't see issues with VCSA on VSAN

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
Reply
0 Kudos
andvm
Hot Shot
Hot Shot
Jump to solution

Thank you for the confirmation regarding storage vmotion the VCSA to vSAN

/storage partition is at 91% usage, is there any from the following which is safe to delete (see some folders are in Gigabytes) ?

andvm_0-1616864949317.png

 

 

Reply
0 Kudos
Ajay1988
Expert
Expert
Jump to solution

U can delete old logs and crash dumps.  Investigate the highlighted one's and majorly  /storage/log/vmware/eam 

Ajay1988_0-1617106543505.png

 

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
Reply
0 Kudos
MrCheesecake
Enthusiast
Enthusiast
Jump to solution

Since upgrading a lot of my VCSAs to 7.0.2, I've been running into more issues where the 10GB disk for logs is now operating consistently in the mid-80% range of utilization and there are no obvious junk files to clean up.

As they've hit the threshold, I've been adding a few extra gigs (usually going from 10 to 14GB) to that drive per this article:

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

Reply
0 Kudos
Ajay1988
Expert
Expert
Jump to solution

Please report via a Support Request and upload the VCSA log bundle

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
Reply
0 Kudos
andvm
Hot Shot
Hot Shot
Jump to solution

there looks to be around 25 or so of similar files:

-rw-r--r-- 1 eam users 147M Feb 10 23:59 localhost_access.2021-02-10.log

Are these ok to delete?

How much % free space should I get it back to?

 

Thanks

Reply
0 Kudos
Ajay1988
Expert
Expert
Jump to solution

Yes. They seem okay to delete

In ur case ; Investigate /storage/log/vmware/eam .
cd to /storage/log/vmware/eam and run du -shc * to check the culprit.

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
Tags (1)
Reply
0 Kudos
andvm
Hot Shot
Hot Shot
Jump to solution

ok it is down to 67% usage and warning has cleared.

Will it just be a matter of time before the logs will accumulate again and I am again with the same issue?

Is this related to any bug or maybe a fix is available by upgrading to a specific VCSA version? (Currently on: Build 17327517)

 

Thanks

Reply
0 Kudos
Ajay1988
Expert
Expert
Jump to solution

Depends on what was cleared and what created them unless it was just old logs not rolled over or cleared.

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
Reply
0 Kudos
milivojacsrdjan
Contributor
Contributor
Jump to solution

Hello. I have problem with storage log space. 

VMWare is 6.7.0.53000 and i would like to know what I can do with old logs, because they are filling my disk.

33GB is used by 2 files. I don't want to expand disk no more as solution. Can I delete some of this files or run some kind of working script?

Screenshot and used space in attachment

 

Thank you in advance

Reply
0 Kudos
Ajay1988
Expert
Expert
Jump to solution

the big files are content-library-runtime.log.stdout. * . 

You are hitting this problem. Follow workaround or upgrade to 6.7 U3s or 7.0 U3 latest  :https://kb.vmware.com/s/article/89009

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ