Full inode space on root partition
Cpanel and emails are failing due to the root inod being full.. I've cleared everything I can from the /tmp directory but it still does not appear to be enough.
[root@srv06 tmp]# df -ih /
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/xvda2 6.3M 6.3M 0 100% /
-
I found another post that said to run /usr/local/cpanel/bin/purge_dead_comet_files but that doesn't appear to do anything
0 -
I've run the following had had this result.. There are nearly 6mb in the datastore directory.. Are they safe to delete?
[root@srv06 .cpanel]# cd /root/.cpanel echo "Inode usage for: $(pwd)" ; for d in `find -maxdepth 1 -type d |cut -d\/ -f2 |grep -xv . |sort`; do c=$(find $d |wc -l) ; printf "$c\t\t- $d\n" ; done ; printf "Total: \t\t$(find $(pwd) | wc -l)\n"
1 - caches
2502 - datastore
Total: 25060 -
I deleted a few older files from datastore but its made no difference to what it thinks is in use
0 -
Hey there! The most likely explanation is that there are a very large number of small files somewhere on the server, such as emails, using up all the inodes on the disk. The only way to resolve that issue will be to free up a significant amount of disk space on the machine, as I wouldn't expect a few in /root/.cpanel to make a significant difference.
You can run that command outside of /root/.cpanel to see where a majority of them are being used:
echo "Inode usage for: $(pwd)" ; for d in `find -maxdepth 1 -type d |cut -d\/ -f2 |grep -xv . |sort`; do c=$(find $d |wc -l) ; printf "$c\t\t- $d\n" ; done ; printf "Total: \t\t$(find $(pwd) | wc -l)\n"
0 -
Got this worked out with some help... Millions of session files.
5252016 /var/cpanel/php/sessions/alt-php56
0 -
I'm glad you tracked that down. We have a tool that can help clean up the session files that you can read about at https://support.cpanel.net/hc/en-us/articles/360052249794-How-to-clean-up-PHP-Session-files but for the long-term health of the system, it might be best to find out which user's scripts aren't properly closing their sessions.
0
Please sign in to leave a comment.
Comments
6 comments