MageiaThis forum is for the discussion of Mageia Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all.
I had this exact same problem about a year ago (see: "I need to increase the size of /var - adjacent to an NTFS partition"). In that problem my /var was only 6.8Gb in size. After I re-sized partitions (NTFS and /var) my /var was (and is) 14Gb in size. It too has completely filled up.
I discovered this problem this morning when I tried to install an update, it failed as /var was full.
The main culprits are 3 folders I have found so far:
/var/log - 3.9Gb
/var/lib/plexmediaserver - 3Gb (I expected this but I need to keep that)
/var/spool - 3.7Gb
So what is going on, /var is twice the size now. Why are /log and /spool so huge?????
I don't want to have to go through the rigmarole of re-sizing all the time, that seems ridiculous.
As always, any help greatly appreciated.
Only you can answer that - go have a look.
On one of our netbooks a wifi adapter generated millions of logs - gave GB size kernel and syslog. I just empty them - the compressed rotations are much more acceptable, but no point keeping them either. Short answer - fix the problem.
Thanks for that but of no help. I don't know how to do either of those things you specify - empty the logs or turn on compressed rotational logs. I had a look in the System Logs section of the MCC and couldn't find any way to achieve what you say.
I should say I am using Dolphin to do this, I'm not a CLI-type of guy.
Also in /var/spool/mail/ there is something called "root" that is 3.7Gb big. I can't see anything specific in /var/log taking up 3.9Gb, but there are some folders I can't access in Dolphin.
Do you have logrotate installed? (I would expect it to be by default.) Years ago, I ran into a similar problem on Debian and installing logrotate made it go away. And, no, I don't know why it wasn't already present.
If you do, and /var/log is filling up with log files that logrotate has rotated (they generally end in a number, like [somelog].1, [somelog].2, etc.), perhaps you could write a script to run as a [unit-time] cron job to delete those files.
([unit-time] would be long enough to be reasonably certain that you won't need to consult those archived logs.)
Yes I do have logrotate installed (I just checked) and it seems to have been installed by default. And, yes, it seems to keep 5 logs, 1 current log and 4 previous. So there is something else in one of the other folders in /var/log (some I can't see into with my logon) under Dolphin.
So there's that and there's the /var/spool/mail/root problem.
Yes the results are the same.
I don'think I can move PMS out of /var as that is where it gets installed. I have just asked though. And yes it holds all of the relevant PMS data as well as my media file data descriptions etc. My media files are actually located on an external NTFS drive.
But I am more interested in the contents of some folders within /var/log that I can't access and hold most of the space for that folder as the usual system logs only use about 800Mb. Also more interested in this: /var/spool/mail/root which is what is consuming the entire 3.9Gb of space.
But I am more interested in the contents of some folders within /var/log that I can't access and hold most of the space for that folder as the usual system logs only use about 800Mb. Also more interested in this: /var/spool/mail/root which is what is consuming the entire 3.9Gb of space.
You need to get in there and see what it is.
And about the logs: there's probably a reason why there's too much of it. You need to get in there and see what it is.
Come to think of it, the root mail probably contains the same log messages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.