Debian 11: inode exhaustion on web content volume

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Write operations fail even with free space because available inodes are exhausted.

Environment & Reproduction

Systems return no space left on device while `df -h` appears healthy.

Root Cause Analysis

Run `df -i`, then identify small-file hotspots with `find /var/www -xdev -type f | wc -l`.

Quick Triage

Large numbers of cache, session, or temp files consume inode capacity disproportionately.

Step-by-Step Diagnosis

Purge obsolete small files, rotate caches aggressively, and move high-churn paths to volumes with adequate inode density.

Solution – Primary Fix

Confirm inode recovery using `df -i` and test application writes in affected directories.

Solution – Alternative Approaches

Apply retention policies and scheduled cleanup jobs for cache and session directories.

Verification & Acceptance Criteria

Restore mistakenly removed operational files from backup snapshots if required.

Rollback Plan

Trigger alerts on inode utilization thresholds independent of byte-based disk alerts.

Prevention & Hardening

`df -i`; `find /var/www -xdev -type f | wc -l`; `sudo du -x /var/www -a | sort -n | tail -20`

Related Errors & Cross-Refs

Share filesystem type, inode metrics over time, and top file-count directories.

Related tutorial: View the step-by-step tutorial for debian-11.

View all debian-11 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Choosing filesystem parameters during provisioning affects future inode headroom significantly.