Hi -
1. Here's your output, wrapped in [code] tags:
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 123G 115G 1.6G 99% /
/dev/cciss/c0d0p1 99M 19M 75M 21% /boot
tmpfs 3.9G 0 3.9G 0% /dev/shm
//192.168.5.68/recordings 280G 188G 93G 67% /mnt/callito
191981794 /mnt
2704196 /var
2398380 /usr
224520 /lib
97864 /etc
33988 /sbin
20484 /lib64
13614 /boot
8120 /bin
208 /root
2. You're using 115 of 123GB on "root". Your question is "who on root is the space hog?"
3. The answer appears to be "/mnt".
a) "mnt" is using the most space
... but ...
b) "mnt" really shouldn't be using ANY space.
It should be "empty" - a location where you can "mount" other filesystems!
4. Conclusion -
a) I'm guessing that you probably MEANT to mount some filesystem in "/mnt"
b) ... but the mount failed...
c) ... you didn't catch the mount failure
d) ... and you inadvertantly started writing gigabytes there
5. SUGGESTION:
Code:
umount /mnt/callito
cd /mnt
du -sk *|sort -nr
<= This should identify the space hog :)
IN SUMMARY:
I believe you're probably out of disk space because you might accidentally be writing to "/mnt", instead of to a filesystem you think you have MOUNTED in "/mnt".
Make sense?
Please keep us posted what you find!