Engineering Glossary · Filesystem
Inode — You Have Two Storage Budgets, and the File Count Runs Out First
The panel says the account is full, the disk usage figure says otherwise, and writes are failing anyway.
The short answer
An inode is the filesystem's index entry for a single file or directory, and because hosting plans cap the number of them, it limits how many items an account can hold regardless of their size. Hit the ceiling and writes fail while the gigabyte figure still looks comfortable.
You are therefore spending against two budgets at once. A million small cache fragments exhaust the inode allowance while barely moving the byte count; one large video does the exact opposite. Knowing which budget is short tells you which cleanup will actually help.
By the HostingFast team · Reviewed 24 August 2026
100+
Terms defined properly
2 min
Read time, end to end
Plain
English, no hand-waving
24/7
Engineers on shift
The usual consumers are predictable: cache directories, mail archives where every message is its own file, PHP session files, and dependency trees of the node_modules variety. All four regenerate themselves while nobody is watching.
There is a performance dimension as well as a capacity one. Very large file counts slow down anything that has to walk the tree — backups, rsync, recursive searches and the panel's own disk usage calculation all take longer as the count climbs.
Finding out where the count actually is
The panel's statistics screen shows the live count against your plan's ceiling, which tells you whether you have a problem. Locating it needs the shell: count files per directory and sort the results, and the offender is usually obvious within one command.
Do it at the top level first and then descend into whichever directory dominates. Counting the whole tree at once produces a big number and no information; counting one level at a time produces a culprit.
The four categories that produce millions of files
Application caches come first, and they are the safest to clear because they rebuild themselves. A WordPress site with an abandoned cache plugin can leave 800,000 stale fragments behind — trivial in gigabytes, most of the inode budget, and gone in a single operation once somebody knows where to look.
Then mail, where every message is a separate file; session directories that nobody garbage-collects; and dependency trees checked into the account rather than installed at build time. That last one is the developer speciality: node_modules belongs on a build machine, not in a web root.
What a high file count costs you beyond the limit
Backups take longer, because the cost of copying a million tiny files is dominated by per-file overhead rather than by bytes. The same applies to rsync, to recursive greps, and to any deployment step that walks the tree.
So bringing the count down is not purely a capacity exercise. It shortens your backup window, speeds up your deploys and makes the panel's own usage figures refresh in a sensible time.
Headroom on this platform
Daily backups run on every plan with self-service restores from the panel, and a leaner account is a faster restore as well as a smaller one. NVMe storage keeps per-file overhead low, but no disk technology makes a file count limit disappear.
If the count is genuinely justified rather than accumulated waste, upgrades happen in place from the client area with no migration and no downtime — the range runs from compact shared accounts through VPS to dedicated servers.
Two budgets, counted separately
Most hosting confusion comes from a limit nobody explained. These entries name the limit, show you how to measure your position against it, and say which cleanups genuinely move it.
Daily backups run on every plan and restoring a file or a database is one click in the panel rather than a support ticket.
- 100+ entries with the limits stated
- Shell commands for locating the problem
- Wired into Disk Space, Cache and Backup
- Written by the engineers who clear these
Why HostingFast
Standard on every plan
Two budgets, made explicit
Bytes and file count are separate ceilings, and only one of them is usually the problem.
Inode, located precisely
How to descend a tree one level at a time until the offending directory names itself.
Four usual suspects
Caches, mail, sessions and dependency trees — with the safe order to clear them in.
The performance angle
High file counts slow backups, deploys and searches long before they stop writes.
Developer-specific advice
Dependency trees belong on a build machine, and this entry says so directly.
Continues into its neighbours
Disk Space, Cache and Mailbox Quota carry on from here.
Quick Start
From order to online
- 1
Read the count against the ceiling
The statistics screen in the panel shows both numbers. If the count is near the limit and the byte figure is not, you have found your problem.
- 2
Count one directory level at a time
Total the files under each top-level directory and sort. Descend into whichever dominates and repeat until the culprit is obvious.
- 3
Clear the regenerating categories first
Application caches rebuild themselves, so they are the safest things to purge and usually the largest win.
- 4
Move build artefacts off the account
Dependency trees and build outputs belong on a build machine. Deploying the result rather than the workspace keeps the count flat.
Built In
Loaded onto every plan
- Live file count shown against your plan limit in the panel
- SSH access on developer-focused plans for locating the problem
- Daily backups with one-click self-service restores
- NVMe SSD storage across every tier
- In-place upgrades from shared through VPS to dedicated
- Mailbox management and quotas from the same panel
- LiteSpeed caching at server level on every plan
- Engineers on support at any hour
Frequently Asked
What people ask us most often
The disk says full but the gigabytes say otherwise. What is happening?
You have hit the file count ceiling rather than the storage one. Plans cap both, and the count runs out first on any site that generates many small files. Check the statistics screen for the live count against your limit, and if that is the number at the ceiling, the cleanup you need is about quantity, not size.
Which directory is consuming my file count?
Find it by descending rather than by totalling. Count the files under each top-level directory, sort the results, then repeat inside whichever one dominates. Two or three iterations will name the offender, where a single count of the whole account tells you nothing you did not already know.
Does a high file count slow anything down, or is it just a limit?
It slows things down measurably. Backups, rsync, recursive searches and any deploy step that walks the tree are dominated by per-file overhead rather than by bytes, so an account with a million stale cache fragments has a longer backup window and slower deployments as well as less headroom.
Can I run several websites on one plan?
From the Turbo tier upwards, yes — multiple sites, each with its own domain, mailboxes and certificate, inside a single account. If the extra sites belong to clients rather than to you, reseller hosting keeps each one properly walled off instead.
Keep reading
Mailbox Quota
The storage ceiling on a single mailbox, and what happens when it is reached.
Cache
Work already done and kept — plus the fragments it leaves behind when abandoned.
Best LiteSpeed Hosting
The same call made as a buyer's guide: what to verify and what to ignore.
Domain Names
Find, register and transfer domains — first year free with annual hosting.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and a flat monthly price.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Get the headroom back.
NVMe, LiteSpeed and free SSL on every plan, engineers who answer at any hour, and a renewal price that matches the day you signed up.
View Domain Names plans