Linux Commands / IT Support Guides
Diagnose inode exhaustion with df -i
A server can have free storage bytes and still fail to create a tiny file. Too many small files may have exhausted the filesystem's inode capacity.
Environment and inputs: Linux · Bash-compatible shell; package and service names vary by distribution
Try the diagnostic command
Use the stated shell and platform. Replace sample domains, addresses, services and paths with values from the system you are authorized to support.
df -iHow to read the result
The inode totals and IUse% indicate object allocation on filesystems that report this information. A nearly exhausted inode count differs from running out of data blocks.
What to do next
Identify the affected mount, then inspect likely caches, session stores or spool directories with the service owner. Plan retention changes instead of deleting application state blindly.
Before you make a change
Some filesystem types allocate inodes dynamically or report them differently. Confirm the filesystem behavior before assuming a fixed inode limit.