🟡 Medium   ⏱ 5–30 min  Last verified: 19 May 2026

📖 ~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 filesystem fills unexpectedly because systemd journal files grow without practical retention limits.

Environment & Reproduction

Ubuntu 22.04 with verbose services and persistent journaling enabled under /var/log/journal.

Root Cause Analysis

High log volume plus absent size/time caps allows journald to consume disk until service disruptions begin.

Quick Triage

Check usage via journalctl –disk-usage and df -h, then identify chatty units with journalctl -u and priority filters.

Step-by-Step Diagnosis

Inspect /etc/systemd/journald.conf, validate current RuntimeMaxUse/SystemMaxUse values, and audit log spikes by unit.

Illustrative mockup for ubuntu-22-04-lts — journald_disk_problem
Large systemd journal footprint on Ubuntu 22.04 — Illustrative mockup — Progressive Robot

Solution – Primary Fix

Apply sane journald retention limits, restart systemd-journald, and free space safely with journalctl –vacuum-size or –vacuum-time.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Illustrative mockup for ubuntu-22-04-lts — journald_disk_solution
Journal vacuum and retention policy tuned on Ubuntu 22.04 — Illustrative mockup — Progressive Robot

Solution – Alternative Approaches

Forward logs to rsyslog or centralized stack, lower service log levels, or set rate limits for noisy components.

Verification & Acceptance Criteria

Disk usage stabilizes, log retention remains within policy, and critical services no longer fail due to full partitions.

Rollback Plan

Restore prior journald configuration and reload if new limits reduce forensic retention below compliance needs.

Prevention & Hardening

Standardize log retention baselines, track log growth metrics, and review noisy unit logs in recurring operations checks.

Comparable Ubuntu issues include runaway application logs, Docker json-file growth, and auditd backlog saturation.

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

man journald.conf, man journalctl, Ubuntu logging documentation, and systemd journal best practices.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.