| View previous topic :: View next topic |
| Author |
Message |
ck42
l33t
Joined: 31 Jul 2003
Posts: 789
|
 Posted: Sat Mar 19, 2011 6:13 pm Post subject: Trying to understand my / fs space usage [SOLVED] |
 |
|
Okay...so started getting failed compilations due to not enough disk space. Run df and see that rootfs is 100%. 
I've searched through everything on the partition and things just don't add up (Also cleaned up what little crap even could be deleted - less than 10M). Here's the break down of my setup and what I'm seeing. Can someone help me find Waldo here??
Here's my partition structure:
| Code: | Filesystem Size Used Avail Use% Mounted on
rootfs 981M 972M 0 100% /
/dev/root 981M 972M 0 100% /
rc-svcdir 1.0M 136K 888K 14% /lib/rc/init.d
udev 10M 596K 9.5M 6% /dev
none 1.5G 908K 1.5G 1% /dev/shm
cachedir 4.0M 4.0K 4.0M 1% /lib/splash/cache
/dev/sda5 2.0G 8.8M 1.9G 1% /tmp
/dev/sda6 7.7G 4.8G 2.6G 66% /var
/dev/sda7 39G 15G 22G 41% /usr
/dev/sda8 7.7G 644M 6.7G 9% /opt
/dev/sda9 20G 833M 18G 5% /usr/portage
/dev/sda10 20G 5.1G 14G 28% /usr/portage/distfiles
/dev/sda11 821G 169G 611G 22% /home |
So I've got a 1G rootfs. (what is the difference between rootfs and /dev/root/ ?
Now, here's the df usage for the / and anything else hanging off that partition:
| Code: | 596K /dev
636M /mnt
8.0K /certs
499M /opt
76K /tmp
0 /sys
16K /lost+found
84M /root
20K /.snapshots
128K /config
8.0K /.config
18G /usr
129M /lib
10M /bin
3.7G /media
2.5M /boot
15M /sbin
4.0K /.qt
169G /home
4.7G /var
68K /emerge
56M /etc
0 /proc
196G / |
So the big thing that obviously stands out is /mnt
That 636M that is listed is from a mounted NAS on my network where I keep my rsync'd backups. Now....that data is on a separate physical drive....but I realize that /mnt is hanging off of my / partition so it's *technically* part of it, but should it actually be counted as used / partition space? Or is that NOT what's happening here. Regardless of yes/no, I'm still apparently/truly out of disk space due to the compilation failure message.
Last edited by ck42 on Sat Mar 19, 2011 8:18 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54317
Location: 56N 3W
|
| Posted: Sat Mar 19, 2011 6:59 pm Post subject: |
|
|
ck42,
Nothing should ever mounted at /mnt, you should always use /mnt/<something>
I wonder if /mnt really has 636Mb used ... maybe because your NAS didn't attach one time and rsync sent your backup to /mnt ?
A little like copying the kernel to /boot and forgetting to mount /boot
| Code: | rootfs 981M 972M 0 100% /
/dev/root 981M 972M 0 100% / |
are the same thing. It done to avoid having to write code to check for and handle a empty list of filesystems.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
ck42
l33t
Joined: 31 Jul 2003
Posts: 789
|
| Posted: Sat Mar 19, 2011 8:03 pm Post subject: |
|
|
You're right that nothing should be writing in /mnt....but I think something was. My rsnapshot.conf file points to the appropriate directory for the rsnapshot image to be sent to (/mnt/nas) *BUT* it appears that for whatever reason, nfsmount was not setup in rc-update to run at default. So it looks like what was happening was that rsnapshot was dumping the backups into the directory path that it 'expected' to be there.....but because the NAS wasn't NFS mounted, it just dumped it into /mnt/nas/
testing this now, but I think that solves the mystery. Thanks for pointing me the right direction, Neddy!
UPDATE: Yep. That was it.  |
|
| Back to top |
|
|
|
Other Things Gentoo
