Inode Usage With CPanel Hosting Print

  • #DecreasingInodeUsageWithCPanelHosting, #indoesandcpanel, #cpanel, #inodes
  • 0

 Inode Usage With CPanel Hosting

Most people will not need to be familiar with Inodes if they are using their hosting in normal circumstances such as for a basic or intermediate website and normal email use. However, to ensure that all our customers get a consistently high level of service we have implemented inode limits per account for reducing resource abusers in our Shared Hosting and Reseller hosting.

Not all inode overages are caused by abuse though. It could just be that you need to do a bit of a clean up of your hosting files. If you experience issues caused by high Inode usage then this tutorial is to help you decrease the number of inodes on your account.

Here are some steps to reduce the inode number limit.

1) Delete Unnecessary Files And Folders

Examine the files and folders manually and decide on if the file is necessary or not. In case if the file is an old backup archive or if the folder is created for testing or staging purpose, you may remove it or download it locally via FTP or cPanel >> FileManager and delete it from the server.

2) Clear Old And Spam Emails

Deleting the old emails helps a lot in decreasing the inode usage. There might be spam mails in your mailbox which are of no use and deleting those mails will hep you to reduce the inode number. You can remove spam emails from email client or webmail. You can seek help from our support department which operates 24*7 to delete the mails easily via shell.

3) Clear The  Cache Files

Most of the CMSs uses cache to reduce the response time and application like Joomla can create a lot of cache files which can increase the inode usage tremendously. So it is advised to keep an eye on the cache folders and make sure the number of cache files is the least.

Most of the CMSs now provide the facility to purge the cache and you can make use of it to control the number of cache files. Or you can setup a cronjob to automatically clear the cache files periodically.


Was this answer helpful?

« Back

Powered by WHMCompleteSolution


["\r\n