Disk Space Not Recovered After Deleting Large Log Files

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

df -h remains high even after deleting very large log files from disk.

Environment & Reproduction

A running process still keeps file descriptors open to deleted files.

Root Cause Analysis

Run: sudo lsof +L1 | grep deleted to identify lingering open deleted files.

Quick Triage

Map each PID to its systemd service and evaluate if safe restart is possible.

Step-by-Step Diagnosis

Capture lsof output proving space is still tied to active process handles.

Solution – Primary Fix

Capture reclaimed space after controlled service restart.

Solution – Alternative Approaches

Identify owner service: ps -fp and systemctl status .

Verification & Acceptance Criteria

Restart process gracefully: sudo systemctl restart .

Rollback Plan

Use logrotate policy updates to avoid manual deletion patterns causing recurrence.

Prevention & Hardening

Verify space return with df -h and ensure lsof +L1 no longer lists large deleted files.

Related Errors & Cross-Refs

Configure journald and logrotate retention with realistic size/time caps.

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

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

If restart impacts service, roll back config and return to previous stable process settings.