SlackwareThis Forum is for the discussion of Slackware 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.
My root partition (/dev/sda1) is full. Okay, I know this is frequently asked, but the time has finally come. I've been trying to solve this problem for a few months. I'm running Slackware 12.1 with jfs on / and /home, but this still happened on 12.0 when I was running reiserfs on both.
This is not necessarily cause for concern (everything still runs fine), except that
* Sometimes when I untar something, I get "no space left on device"
* I had a 6gb root partition, then when I installed Slackware 12.1 (fresh install), I made /dev/sda1 10gb, thinking that would prevent it from filling up
* I can't find the offending files; I've searched every Linux and Unix forum and mailing list on the web, and the usual suspects (/var/log, /tmp, /var/tmp) are not the culprits; each user has $TMP set to his or her own ~/tmp, as well as KDEVARTMP=~/tmp
* I was running sshd, thinking that /var/log/messages was filling up with ssh attacks; now that I've shut it off, deleting /var/log/messages does not solve the problem
* I run rsync backups nightly -- could it be stowing temporary files someplace?
So the real problems are:
* What causes it? i.e. how do I stop this from happening?
* How do I find the offending files, and delete them?
I've tried all the du, df, find and all that, and I don't find any single file that's over a gigabyte. Any other ideas?
Like I said, this is mainly irritating because of the occasional errors when "manually" installing (or updating) software, and that I don't know why it's happening.
Another note, I had a similar installation at work, running similar backups, and this never happened. That was behind a VPN.
*MY* usual way of doing this is to do "du -h --max-depth=1 /" and then see the main offenders in terms of top level directory, then replace / with /tmp, /var etc... as that command gave you, and then just keep localising it. i'd certainly assume it'd be something in /var unless you've just generally been install happy, with vast amounts of data in /usr
You could trim your installation to allow more space on '/dev/sda1'. Or you could attach another drive with more space to your '/'. A good candidate would be to move your '/usr' to that available space then mount via your '/etc/fstab'. Just make sure that you have growth on the new '/usr/'. Looking at your '/dev/sdb1 39G 5.0M 39G 1% /mnt/hd' indicates good place to start.
I guess that means I have been "install-happy." I did install Gnome and a few other things. I will delete some stuff and see how long it takes for this to happen again. I certainly don't need vim :P
I like having sshd running, but it's useless sine I'm moving in three days.
Quote:
Originally Posted by shadowsnipes
You didn't do anything weird and set your block sizes huge did you?
Hmmm...my operations have been low on the weirdness side. All I've done is install software (I didn't think I could have installed 5GB, but it looks like I did). Can you clarify? What would I have done to set the block size of what to do what?
I was saving the /,/usr,/var,/tmp,/home setup for my next install, but maybe I should have done it this time.
Thanks so much --- this forum is great,
Joel
Last edited by trashbird1240; 05-26-2008 at 03:34 PM.
It's weird because your / partition according to df has 9.3GB, but du only shows 5.7GB. 3.6GB is a lot to be unaccounted for.
I'm guessing that your space got filled up because of GNOME. 9.3GB is plenty of room for a full slack install and quite a few packages. GNOME probably took up the rest. What GNOME did you install and how did you do it?
For completeness, you might want to add a --apparent-size to the du command to see if it differs (is bigger).
One thing that might be worth checking is whether anything is hiding underneath your mount points in /mnt or /media.
If your backup script failed to mount the /mnt/backup for example but didn't catch the error and continued on regardless it would write data into the /mnt/backup directory in the root filesystem. Then when a later run sucessfully mounts that filesystem it hides the fact this has happened. I'd suggest unnmounting /mnt/hd /mnt/backup and /media/multimedia etc.. if possible and run the du's again to check whether this is what has happened.
edit: underneath /home might also be worth a look if you find nothing anywhere else.
Did you already reboot your system? If not, there might be a process hanging around, that keeps a deleted file open. lsof | fgrep 'deleted' should give you a hint, if there's an open, but deleted file, that invisibly occupies 3G of your hd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.