Ubuntu 16.04 Disk Space Suddenly Full Due to Journal Logs

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

Filesystem usage spikes to near 100 percent, causing application write failures and alerts.

Environment & Reproduction

Appears on long-running hosts with verbose services and unbounded journal retention.

Root Cause Analysis

Persistent logs accumulate without size limits, exhausting root or var partition capacity.

Quick Triage

Measure top disk consumers and verify journal size and rotation status.

Step-by-Step Diagnosis

Use disk usage tools and journalctl –disk-usage to identify runaway logging sources.

Solution – Primary Fix

Vacuum old journal files, set retention limits, and address noisy service log patterns.

Solution – Alternative Approaches

Forward logs externally, adjust rsyslog policy, or move logs to dedicated partition.

Verification & Acceptance Criteria

Disk usage returns to safe thresholds and log growth remains within configured limits.

Rollback Plan

Restore prior journald settings if retention changes affect required audit coverage.

Prevention & Hardening

Set explicit log retention policies and monitor partition usage with proactive alerts.

Related Errors & Cross-Refs

Related to no space left on device errors and failed package installations.

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 log management documentation for retention tuning.