RHEL 8 XFS Inode Exhaustion Despite Free Disk Space

📖 ~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

Applications fail creating files even with free capacity, causing queue backlogs and ingestion failures.

Environment & Reproduction

Run df -i and attempt file creation in affected path to observe inode-related write errors.

Root Cause Analysis

Huge counts of tiny files from cache, spool, or log sharding consume available inode metadata.

Quick Triage

Identify high file-count trees with find and check recent growth from application cron jobs.

Step-by-Step Diagnosis

Measure inode usage by directory, correlate with service logs, and validate cleanup safety.

Solution – Primary Fix

Purge obsolete small files, tune retention, and redesign file sharding strategy to reduce inode churn.

Solution – Alternative Approaches

Migrate high-churn paths to object storage or database-backed queues where appropriate.

Verification & Acceptance Criteria

df -i shows healthy headroom and application file creation works continuously under load.

Rollback Plan

Restore archived files from backup if cleanup removes data needed for audit or replay.

Prevention & Hardening

Set inode growth alerts and enforce automatic cleanup of temporary and spool directories.

Related Errors & Cross-Refs

Related: No space left on device with free GB, failed open(), and queue spool overflows.

Related tutorial: View the step-by-step tutorial for rhel-8.

View all rhel-8 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Consult XFS and RHEL 8 storage troubleshooting documentation.