Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a dedicated server with OVH. Problem is that i keep receiving warnings that the / is getting full. Yesterday it was 89%, today it is 90% and tomorrow it will probably be 91%. It keeps increasing everyday. Once it gets full, the whole server gets locked and cPanel stop working until i clean the disk. I had a friend check the disk and try to clean the useless files but he didn't find where it is coming from. My server have a 1TB disk but the partition that gets full is only 20GB. Of course OVH is helpless so i thought i'd come here and ask for help. I'm a newbie with server management stuff, so if it is complicated to fix this problem i'd rather pay someone to do it for me. I'm a bit scared about increasing the partition size, i fear i could lose my files if something goes wrong. So i'd rather find out what keeps filling the 20GB partition.

Here's the warning message i keep receiving:

DISKWARN: / on ks4002097.ip-198-100-146.net ( 16.89/19.84 GB - 90%
The file system rootfs, which is mounted at /, has reached warn status because it is 90% full.
Server: ks4002097.ip-198-100-146.net
Primary IP:
Notification Type: diskwarn
Filesystem: rootfs
Mount Point: /
Percentage Full: 90%
Disk Information:

Used: 16.89GB
Available: 1.96GB
Total: 19.84GB

ChkServd Version: 15.2 

More infos:

for i in ls / | grep -v "\."; do du -skh /$i;done

    186M /backup/
7.6M /bin/
13M /boot/
144K /dev/
79M /etc/
30G /home/
1.4M /installd/
536K /latest
26M /lib/
25M /lib64/
16K /lost+found/
4.0K /media/
4.0K /mnt/
522M /opt/
du: cannot access `/proc/13067/task/13067/ns/net': No such file or directory
du: cannot access `/proc/13067/task/13067/ns/uts': No such file or directory
du: cannot access `/proc/13067/task/13067/ns/ipc': No such file or directory
du: cannot access `/proc/13067/ns/net': No such file or directory
du: cannot access `/proc/13067/ns/uts': No such file or directory
du: cannot access `/proc/13067/ns/ipc': No such file or directory
du: cannot read directory `/proc/13082': No such file or directory
0 /proc/
15M /root/
39M /sbin/
du: cannot access `/scripts@': No such file or directory
20K /selinux/
4.0K /srv/
0 /sys/
2.2M /tmp/
5.6G /usr/
9.3G /var/ root@ks4002097 [~]#

root@ks4002097 [~]# du -sh * 
4.0K anarchoi.sql 
12K cpanel3-skel 
4.0K cpmove 
5.8M etc.130610.tgz 
4.0K installer_la_cle.sh 
4.0K list 
24K mail 
4.0K perl5 
40K php.ini.new 
40K php.ini.orig 
4.0K public_ftp 
8.0K public_html 
3.9M tmp 
root@ks4002097 [~]#

root@ks4002097 [~]# df -h 
Filesystem Size Used Avail Use% Mounted on 
rootfs 20G 17G 2.2G 89% / 
/dev/root 20G 17G 2.2G 89% / 
none 3.9G 140K 3.9G 1% /dev 
/dev/md2 904G 30G 829G 4% /home 
tmpfs 3.9G 4.0K 3.9G 1% /dev/shm 
/dev/loop0 485M 13M 447M 3% /tmp 
/dev/loop0 485M 13M 447M 3% /var/tmp

All i can see in the logs is everyday those process take too much CPU

root 99.7 [migration/2] root 99.6 [migration/2] root 99.5 [migration/2]

share|improve this question
This is most likely log file(s) in /var/log that need to be rotated, archived and deleted on a regular basis. IN particular you probably deleted a log file but didn't restart the associated daemon so it's still holding on to the disk space. We have a bunch of Q&A about it. serverfault.com/search?q=disk+full –  Iain Oct 12 '13 at 5:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.