Inode

An inode is the metadata record for one object on a Linux filesystem: its size, permissions, timestamps, and where its data sits on disk. Not just files count, directories use one too, so every folder adds to the total. The inode limit is a file-count cap, separate from your GB quota. Once inodes run out the server refuses to create new files even when space is free: uploads fail, incoming mail can bounce, and caches cannot write.

Why they vanish while disk looks fine

One huge file uses a single inode, exactly like one empty small file. What eats the allowance is thousands of tiny files: mail folders and attachments, PHP session files never cleared, plugin cache fragments, leftover CMS installs, and dependency trees such as node modules. On shared hosting, mail left on the server and a cron job that writes small cache files are quiet drains that never show on the disk graph.

Counting files yourself

From SSH, run this in your home folder to see how many entries live under it:

find . | wc -l

That command counts every file and directory below the current point. To find the heaviest folders, loop over find . -maxdepth 1 -type d and compare the entry totals per directory. On quota-backed hosts, df -h shows space used and df -i shows the inode table; where those are unavailable, cPanel usually prints the inode figure on the dashboard next to disk usage.

Cleaning up what actually helps

Deleting one big archive barely moves the number, since it used just one inode. What helps is removing thousands of small files in mail, cache, session, or a stale CMS install left over from a migration. Archive old mail outside the document root, turn on auto-purge in cache plugins, and keep backups off the account so they are not counted twice.

The inode limit is not the disk quota

The two caps are independent. An account can sit well under its disk quota yet still be blocked by the inode limit, so free space in the panel does not mean you can write. In practice, running out of inodes shows up as a disk quota exceeded error while GB usage looks normal. On a VPS or dedicated server the filesystem still tracks inodes, but it rarely becomes a daily problem because the cap comes from the filesystem size rather than a per-account policy.

FAQ