You are not logged in.
so, starting a few minutes ago I can't start almost any program because my / is full. Here's some info:
df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 208K 9.8M 3% /dev
/dev/disk/by-uuid/c8107b16-a8c6-4cf7-bb0d-fbda308e9b0a
19G 18G 0 100% /
shm 1005M 0 1005M 0% /dev/shm
/dev/sda4 120G 1.7G 112G 2% /home
/dev/sda3 9.2G 235M 8.5G 3% /var
/dev/sda1 183M 33M 141M 19% /boot
/dev/sdb1 917G 685G 186G 79% /stor
/dev/sdc1 688G 262G 391G 41% /backup
I only have installed Xorg, openbox, XBMC, rtorrent and apache... I think it's not much. I have no idea where to start checking for used space. Please help!
Last edited by RaisedFist (2010-12-01 18:21:17)
Offline
I'd recommend installing ncdu, but since you're out of free space...
"du /" and see where the big files are. Might be some work. Maybe you can make life easier. See "man du" for more info.
Offline
well, I wanted to recommend checking /var/cache but it has a separate partition...in the beginning check every 'main directory' on / with du -h (or du -uh ? unfortunatelly I am on m$ right now...so...sry) this gives you a hint where the root of evil may hide...and than go just deeper to find the source..
EDIT: ncdu is good too, I just forgot the name of it.
Last edited by linux-ka (2010-11-30 14:06:53)
Offline
Try going through your filesystem with
du -mshc *
start at /, have a look at the biggest folders, enter them and issue the command again.
I'm sure, there are programs to analyze your hole filesystem with a nice chart or something, but that's my first idea
Offline
I did this, not sure if it's fine:
du -hcs /bin /dev /etc /lib /lib64 /lost+found/ /media/ /mnt/ /opt/ proc/ /root/ /sbin/ /srv/ /sys /tmp /usr
5.3M /bin
208K /dev
5.1M /etc
233M /lib
4.0K /lib64
16K /lost+found/
12K /media/
4.0K /mnt/
74M /opt/
du: cannot access `proc/1590/task/1590/fd/3': No such file or directory
du: cannot access `proc/1590/task/1590/fdinfo/3': No such file or directory
du: cannot access `proc/1590/fd/3': No such file or directory
du: cannot access `proc/1590/fdinfo/3': No such file or directory
0 proc/
31M /root/
9.6M /sbin/
2.8M /srv/
0 /sys
16K /tmp
1.6G /usr
2.0G total
Offline
I installed ncdu and it shows the same thing as du. Still, is this OK?
Name: proc
Path: /
Type: Directory
Disk usage: 0.0 B (0 B)
Apparent size: 128.0TiB (140.737.486.334.882 B)
Last edited by RaisedFist (2010-11-30 14:24:43)
Offline
what kind of fs? try to run fsck on it.
Offline
Check your /var/cache/pacman/pkgs dir. Usually, there's a ton of stuff there. Pacman stores all it's pkg's there. I have a laptop that has a 20G / partion and I have to keep an eye on that. I usually do a 'cd / ; du sk * | sort -n' delete a few of the bigger files immediately to get some space back so things work. pacman -sc can help. man pacman will also help.
Registered Linux User #402088
Offline
see OP, /var is a single partition
Offline
Check if you are run out of inodes:
df -i
Kind regards, enrique
Offline
Check your /root directory.... as root, not sudo. Sometimes there's a lot of shit in there, and it happens to me a couple of months ago. For an unknown reason, all data that I used to delete with my file manager (vifm) was moved directly to /root/.local/share/Trash ... tons of GB...
arst
Offline
I would go with the inodes thing too, although that usually doesn't confuse df to the point where it thinks the partition is full.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 256808 1107 255701 1% /dev
/dev/disk/by-uuid/c8107b16-a8c6-4cf7-bb0d-fbda308e9b0a
1221600 97880 1123720 9% /
shm 257090 1 257089 1% /dev/shm
/dev/sda4 7929856 1681 7928175 1% /home
/dev/sda3 610800 16844 593956 3% /var
/dev/sda1 48192 34 48158 1% /boot
/dev/sdb1 61054976 60516 60994460 1% /stor
/dev/sdc1 45793280 34427 45758853 1% /backup
so, no, iinodes are fine.
@teh: /root is almost empty, not many files. I rarely use root user.
Offline
again, have you performed a fsck on your fs?
Offline
Ok, so I've resized the partition adding 5GB, but I still don't get why it's showing like this. Here's how it is now:
df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 208K 9.8M 3% /dev
/dev/disk/by-uuid/c8107b16-a8c6-4cf7-bb0d-fbda308e9b0a
24G 18G 4.5G 80% /
shm 1005M 0 1005M 0% /dev/shm
/dev/sda4 114G 1.9G 106G 2% /home
/dev/sda3 9.6G 426M 8.7G 5% /var
/dev/sda1 183M 33M 141M 19% /boot
/dev/sdb1 917G 692G 180G 80% /stor
/dev/sdc1 688G 262G 391G 41% /backup
Offline
It was already suggest in this thread, but can you cd to / and check (or post if unsure) the output of:
du -scm .[!.]* * | sort -n
It should list all (hidden) files and directories in the order of megabytes.
Offline
It was already suggest in this thread, but can you cd to / and check (or post if unsure) the output of:
du -scm .[!.]* * | sort -n
It should list all (hidden) files and directories in the order of megabytes.
Yes, and what should I do with it? It looks like this:
0 proc
0 sys
1 dev
1 lib64
1 lost+found
1 media
1 mnt
3 srv
6 bin
6 etc
9 root
10 sbin
27 boot
236 lib
277 var
361 opt
1426 tmp
1765 home
1776 usr
268067 backup
714431 stor
988392 total
I don't know how this helps...
Offline
...
It tells you where the most space is being used, so you can go there and delete stuff.
Offline
Apparent size: 128.0TiB (140.737.486.334.882 B)
Well, am I the only one being puzzled about a 128 Terabyte /proc?
Offline
the point goes to sherlock Awebb
Offline
RaisedFist wrote:Apparent size: 128.0TiB (140.737.486.334.882 B)
Well, am I the only one being puzzled about a 128 Terabyte /proc?
That's only the apparent-size of /proc, which is a pseudo filesystem. It doesn't show a real disk usage (which is on /proc absolute useless). I will get the same when using ncdu and toggle with the 'a' key.
I guess the point will go to falconindy.
@RaisedFist: Boot your system (best in single user mode) and umount every block device mounted under / (/var, /home, /boot, /store, /backup)
Then look again with ncdu or maybe better:
du -hxcd1 / |sort
I think (like falconindy) that you will have data stored on the blockdevice of / which get later overlayed by your mounts.
You also could boot from an cd/usb an mount your / device and look then with df / du or whatever.
A corrupted FS is also better checked from an external boot medium.
What filesystem do you user on / ?
Last edited by GerBra (2010-12-01 10:51:27)
Offline
Awebb wrote:RaisedFist wrote:Apparent size: 128.0TiB (140.737.486.334.882 B)
Well, am I the only one being puzzled about a 128 Terabyte /proc?
That's only the apparent-size of /proc, which is a pseudo filesystem. It doesn't show a real disk usage (which is on /proc absolute useless). I will get the same when using ncdu and toggle with the 'a' key.
So it's only the theoretical maximum size of the virtual file system. *takes note*
Offline