Re: Filespace exhaustion on '/' partition
On 11/05/2014 16:10, Andrei POPESCU wrote:
On Du, 11 mai 14, 15:33:38, Ron Leach wrote:
We seem to have filled the available space on the '/' partition of our NFS
server. Because most of the server's variable data is on separate
partitions, I'm not sure what I could remove from '/' partition. df shows
the problem, and the space available on the other partitions:
server4:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md1 2919360 2919324 36 100% /
If Im reading this figures correctly ('df -h' is much nicer) your / has
somewhere near 2,8 GiB and is full. Considering you have separate /usr
(which has only some 1,2 GiB) and /var this sounds fishy.
2,9 GiB for / with separate /usr and /var should be plenty. I'd suggest
looking into what is using all that space.
See if unused Linux images are installed
dpkg -l linux-*
Assuming 'un' means not installed, this looks ok:
server4:/# dpkg -l linux-*
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
un linux-doc-2.6. <none> (no description available)
un linux-image <none> (no description available)
un linux-image-2. <none> (no description available)
ii linux-image-2. 2.6.26+17+lenn Linux 2.6 image on
PPro/Celeron/PII/PIII/P4
ii linux-image-2. 2.6.26-25 Linux 2.6.26 image on
PPro/Celeron/PII/PIII/
un linux-initramf <none> (no description available)
un linux-kernel-l <none> (no description available)
un linux-latest-m <none> (no description available)
un linux-modules- <none> (no description available)
ii linux-sound-ba 1.0.17.dfsg-4 base package for ALSA and OSS sound
systems
server4:/#
You might want to check the output of
du / -hx --max-depth=1
To see where the 2,9 GiB are, but my bets are on /opt ;)
server4:/# du / -hx --max-depth=1
0 /var
0 /nfs
1.0K /boot
1.0K /boot2
0 /home
4.0K /tmp
0 /usr
80M /etc
0 /media
64M /lib
5.0M /sbin
0 /selinux
4.1M /bin
0 /dev
0 /proc
12K /mnt
12M /root
0 /sys
0 /srv
0 /opt
165M /
server4:/#
This doesn't suggest anything like 2.8GB, does it? (du does include
the content of sub-directories in its calculations, doesn't it?)
Your math was fine, but here's df -h for clarity
server4:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md1 2.8G 2.8G 36K 100% /
tmpfs 501M 0 501M 0% /lib/init/rw
udev 10M 808K 9.3M 8% /dev
tmpfs 501M 0 501M 0% /dev/shm
/dev/md6 1.8T 1.4T 406G 78% /nfs
/dev/sda1 313M 16M 281M 6% /boot
/dev/sdb1 313M 16M 281M 6% /boot2
/dev/md5 38G 2.4G 35G 7% /home
/dev/md4 949M 4.3M 945M 1% /tmp
/dev/md2 9.4G 1.2G 8.2G 13% /usr
/dev/md3 4.7G 773M 3.9G 17% /var
server4:/#
md is raid1, and xfs. I tried fsck to see if there was some kind of
problem, but it refused to check an xfs filesystem. xfs_check,
itself, declined to run because /dev/md1 is mounted, and rw.
Running du to two levels reveals largest quantities for:
80M /etc
76M /etc/webmin
11M /root/.thumbnails
But there's nothing remotely approaching 2.8GB .
I'll try and look round the filesystem, I imagine xfs will log
something somewhere if it notices something wrong. I would like to
check the fs; if I recall, the system checks the xfs filesystem during
start up so, perhaps later today, I could take the system offline and
reboot it to force a check.
regards, Ron
Reply to: