/dev/root is showing full

[zontrakulla]

[email protected] [/dev]# df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                9.8G  9.4G     0 100% /
/dev/root             9.8G  9.4G     0 100% /
devtmpfs              3.9G  440K  3.9G   1% /dev
/dev/md2              907G  485M  860G   1% /home
tmpfs                 3.9G     0  3.9G   0% /dev/shm
/dev/loop0            485M   11M  449M   3% /tmp
/dev/loop0            485M   11M  449M   3% /var/tmp
/dev/root             9.8G  9.4G     0 100% /var/named/chroot/etc/named
/dev/root             9.8G  9.4G     0 100% /var/named/chroot/etc/named.rfc1912.zones
/dev/root             9.8G  9.4G     0 100% /var/named/chroot/etc/rndc.key
/dev/root             9.8G  9.4G     0 100% /var/named/chroot/usr/lib64/bind
/dev/root             9.8G  9.4G     0 100% /var/named/chroot/etc/named.iscdlv.key
/dev/root             9.8G  9.4G     0 100% /var/named/chroot/etc/named.root.key

[email protected] [/dev]# cd /dev/root
-bash: cd: /dev/root: No such file or directory

 

[zontrakulla]

It's fine now after a reboot. Well..

 

[cPanelMichael]

Hello

There could have been open file handles for deleted files that were closed with the reboot. I am happy to hear you were able to resolve the issue.

Thank you.

 

[zontrakulla]

Actually i remembered that i had symlinked /dev/root to /dev/md1. I don't know why. I removed the symlink and rebooted, and this fixed.

 

[24x7server]

It is nice to here that this issue has been fixed, if faces same issues ahead then you can also have a look on some of server logs files which could be present in GBs. Also if your MySQL directory is having big data size then you can move them in /home drive and make a symlink for it from /var/lib/ as this case is majorly found in same problems.

I can see that your / drive is only having 10G space then above setting is highly recommended.

 

[faisikhan]

It is nice to here that this issue has been fixed, if faces same issues ahead then you can also have a look on some of server logs files which could be present in GBs. Also if your MySQL directory is having big data size then you can move them in /home drive and make a symlink for it from /var/lib/ as this case is majorly found in same problems.

I can see that your / drive is only having 10G space then above setting is highly recommended.

Strongly agreed with you guys, may be that issue can happen again. So it would be better to check the disk usage in detail before rebooting the server as a reboot is not a permanent fix. Usually most of the space is occupied by the logs etc, so you need to empty those files or just remove if these are of no use to you.