systemd-journald consuming excessive 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

Disk space decreases rapidly due to unbounded journal retention.

Environment & Reproduction

Ubuntu 16.04 nodes with verbose logging and default journal sizing behavior.

Root Cause Analysis

Retention and max-size settings are absent or too high for available storage.

Quick Triage

Check current journal disk usage and recent log volume spikes.

Step-by-Step Diagnosis

Inspect journald settings, usage reports, and high-frequency log sources.

Solution – Primary Fix

Set explicit journald size/retention limits and vacuum old logs safely.

Solution – Alternative Approaches

Forward logs to centralized storage and reduce local verbosity levels.

Verification & Acceptance Criteria

Journal size remains within configured limits over normal operation.

Rollback Plan

Restore previous journald config if troubleshooting visibility is reduced.

Prevention & Hardening

Monitor journal growth and define per-host log retention standards.

Related Errors & Cross-Refs

No space left on device and excessive log write amplification.

Related tutorial: View the step-by-step tutorial for Ubuntu 16.04 LTS.

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald and Ubuntu logging configuration documentation.