Understanding and How to Know Inode on Hosting

Posted on

The inode is a data structure that contains information for an object from the file system (it can be a file or directory). Thus, there will be an inode to each file or directory contained in Linux.

The data structure of the inode will be used by the system to identify a file or directory. The information stored in the Inode is:

  • File type
  • Permissions
  • Ownership (including its group)
  • File size
  • A time (Access time), Mtime (modified time) and CTime (change time)
  • Amount of softlinks and/or Hardlinks
  • ACL/Access Control List

By humans, the object of the file system is known as the filename or directory name. As with the system, the object is known from its inode.

What affects the number of inodes in Unlimited Hosting?
In accordance with the above explanation, the number of inodes equals the number of files and directories contained in a single account. If inside your account there are 2 directories with 10 files, then you use 12 inodes. For 3 directories and 15 files, there will be a total of 18 inodes. And so on.

In which directory does the inode of the hosting account be counted?
The inode count will be done on the home directory of your hosting account. Files emails, file websites, caches, temporary files that are in your hosting account will be counted as an inode.

How do I see the number of inodes on my hosting account?
In cPanel, the inode can be viewed through the right sidebar
Inodes limitation

Inode in Hosting

What happens when the use of inode exceeds the AUP limit?
After exceeding 75,000, the hosting account will be excluded from the weekly backups.

If the use of inode continues to grow until the number 250,000, then the addition of files cannot be done on your hosting account and will greatly affect the services contained therein, including email, website, databases, etc.

Why are weekly backups disabled when the inode reaches a certain threshold?
In cPanel, the backup process goes by (1) copying the files to be backed up to another directory, then (2) compressing the data against the directory. In the process of compressing data, the CPU will work more heavily if the number of files being compress is large enough. So it can cause server performance-as a whole-to be decreased.

How to prevent the use of inode exceeds the limit?

  1. Control the use of files and folders. Make sure you delete any files or directories and emails that you no longer use.
  2. Check the cache usage. If your website application uses the cache, make sure that you (or the script you are using) do purge/purge of the old cache and are no longer used by your website.

Thank you and see you…..

Leave a Reply

Your email address will not be published. Required fields are marked *