Inode limit reached Print

  • diskspace, caching, email, backup, domainrenewal, filemanager, uploads, guide
  • 0

Too many files, regardless of their size.

WHAT AN INODE IS

One file or directory, whatever its size. The limit counts items, not bytes.

WHY IT MATTERS

An account well under its disk limit can be at its inode limit, producing the same failures: uploads refused, mail undelivered, writes failing.

WHERE THEY ACCUMULATE

Cache directories, which generate very many small files Session files Email, since each message is a file Backup tools storing files individually rather than archiving Node modules and dependency directories Log files rotated daily

FINDING THEM

Over SSH, count files per directory to identify the largest contributors.

In File Manager, the usual suspects are cache, sessions and mail directories.

CLEARING THEM

Purge application caches, which frequently reclaims a large share Clear old session files Empty Trash and Junk in mailboxes Remove old backups Remove dependency directories not needed in production

PREVENTING IT

Configure cache expiry rather than letting it grow indefinitely Archive rather than storing many files Check the statistics panel monthly


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot