🟠 High   ⏱ 5–30 min  Last verified: 20 May 2026
Affected versions: Ubuntu 24.04 LTS

πŸ“– ~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 volume reaches 100 percent, causing service disruptions and failed writes.

Environment & Reproduction

Seen on systems with verbose logging and no journal retention policy.

df -h /

Root Cause Analysis

systemd-journald persisted logs grew beyond available disk capacity.

Quick Triage

Identify largest consumers under /var and quantify journal size.

sudo du -sh /var/log/journal
sudo journalctl --disk-usage

Step-by-Step Diagnosis

Review high-volume units contributing to log growth.

sudo journalctl -p warning -n 200
sudo journalctl -u snapd -n 100
Illustrative mockup for ubuntu-24-04-lts β€” journal_full_diag
Disk usage spike from systemd journal files β€” Illustrative mockup β€” Progressive Robot

Solution – Primary Fix

Vacuum old logs and configure journal size limits.

Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

sudo journalctl --vacuum-time=7d
sudo journalctl --vacuum-size=500M
sudo systemctl restart systemd-journald
Illustrative mockup for ubuntu-24-04-lts β€” journal_full_fix
Vacuuming journal and setting retention limits β€” Illustrative mockup β€” Progressive Robot

Solution – Alternative Approaches

Forward logs to centralized logging and reduce local retention windows.

sudo sed -n '1,120p' /etc/systemd/journald.conf

Verification & Acceptance Criteria

Free space recovers and journald respects configured limits.

df -h /
sudo journalctl --disk-usage

Rollback Plan

Restore previous journald configuration if retention policy is too strict.

sudo cp /etc/systemd/journald.conf.bak /etc/systemd/journald.conf
sudo systemctl restart systemd-journald

Prevention & Hardening

Set explicit SystemMaxUse and monitor /var growth with alerts.

Frequently accompanies apt failures and database errors due to no space left on device.

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

View all Ubuntu 24.04 LTS tutorials on the Tutorials Hub β†’

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald retention and storage control documentation for Ubuntu.

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.