Ubuntu 22.04 LTS – disk fills from oversized journald logs – 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

Root partition approaches 100% usage, causing package failures and service instability.

Environment & Reproduction

Common where verbose services emit high-volume logs without retention caps.

Root Cause Analysis

Persistent journal storage with no size limits allows indefinite log growth under noisy workloads.

Quick Triage

Identify top directories and confirm journald contribution before deleting files.

Step-by-Step Diagnosis

Examine log rates and service sources that flood journals.

Solution – Primary Fix

Vacuum old journals and define persistent size/retention in journald configuration.

Solution – Alternative Approaches

Forward logs to centralized systems and reduce local retention for edge hosts.

Verification & Acceptance Criteria

Disk usage stabilizes and journald remains within configured limits.

Rollback Plan

Restore original journald.conf values if retention changes conflict with audit requirements.

Prevention & Hardening

Set default retention policies in base images and alert on rapid log growth.

Related Errors & Cross-Refs

Often seen alongside runaway service crash loops and verbose debug-level logging.

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

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald documentation and Ubuntu logging best practices.