Ubuntu 20.04 LTS – journal logs fill root filesystem unexpectedly – Fix & Prevention

📖 ~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 usage rises rapidly on root filesystem, risking service outages and failed package operations.

Environment & Reproduction

More common on verbose services and hosts without explicit journald retention caps.

Root Cause Analysis

Persistent journal storage grows without size limits while high-frequency logs accumulate.

Quick Triage

Measure journal footprint and clear emergency space before changing retention policy.

Step-by-Step Diagnosis

Inspect journald settings, daily log volume, and filesystem growth timeline.

Solution – Primary Fix

Set journal size limits and vacuum old logs to reclaim space immediately.

Solution – Alternative Approaches

Forward logs to centralized pipeline and reduce local retention requirement.

Verification & Acceptance Criteria

Root usage stabilizes and journal growth remains within configured budget thresholds.

Rollback Plan

Restore prior journald config if required diagnostics are lost after tightening retention.

Prevention & Hardening

Establish disk alerts and baseline per-service log rates in operations dashboards.

Related Errors & Cross-Refs

Can trigger apt failures, database write errors, and temporary file allocation issues.

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

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald retention documentation and Ubuntu logging recommendations.