Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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 Leirith, this link has a article which say every directory under /var.
/var/log
Log files from the system and various programs/services, especially login (/var/log/wtmp, which logs all logins and logouts into the system) and syslog (/var/log/messages, where all kernel and system program message are usually stored). Files in /var/log can often grow indefinitely, and may require cleaning at regular intervals. Something that is now normally managed via log rotation utilities such as 'logrotate'. This utility also allows for the automatic rotation compression, removal and mailing of log files. Logrotate can be set to handle a log file daily, weekly, monthly or when the log file gets to a certain size. Normally, logrotate runs as a daily cron job. This is a good place to start troubleshooting general technical problems.
so please check the size of the /var/log. It may be possible that it's size may increase indefinitely.
The problem seems to have resurfaced since I performed the above commands. Something is slowly filling sda6 and /var is staying the same size. Could anyone offer insight into how this could be happening, and what to do about it?
Distribution: Slackware, Debian, Mac OS X, Zenwalk, Puppy, Gentoo
Posts: 199
Rep:
what I do to track down what is taking up space is to use the command:
sudo du -a -h --max-depth=1
this will show you the size of all files and folders in the current directory, just start from the root directory and look which dir has lots of space, cd to that directory and type the command again.
note: you can do this without sudo, but it will probably spit out alot of "permission denied" errors as the command traverses all dirs.
One possibility is open unlinked files; these will not show up in du output but are counted in df's "used" total. See here, here and here for how to find them. rsync is one program that writes to unlinked open files.
One possibility is open unlinked files; these will not show up in du output but are counted in df's "used" total. See here, here and here for how to find them. rsync is one program that writes to unlinked open files.
this helped me.. i had a process running. which when i killed it.. freed a lot of space.. thank you
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.