π ~1 min read
Table of contents
Symptom & Impact
Root partition fills rapidly, impacting service writes and potentially causing read-only remounts.
Environment & Reproduction
Frequent on chatty services without log rate control or journal retention limits.
Root Cause Analysis
journald default retention allows growth beyond expected capacity under sustained high-volume logs.
Quick Triage
Measure journal footprint and identify top log-generating units.
Step-by-Step Diagnosis
Run: sudo journalctl –disk-usage; df -h; sudo journalctl –since ‘1 hour ago’ | wc -l; sudo journalctl -p warning -b | tail -n 50.
Solution – Primary Fix
Set limits in /etc/systemd/journald.conf (SystemMaxUse, RuntimeMaxUse), then run: sudo journalctl –vacuum-size=500M; sudo systemctl restart systemd-journald.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
Solution – Alternative Approaches
Forward logs to centralized collectors and reduce verbose application log levels.
Verification & Acceptance Criteria
Journal storage stays within configured thresholds and disk free space stabilizes.
Rollback Plan
Revert journald.conf changes and restore archived journals if retention policy is too aggressive.
Prevention & Hardening
Enforce log budgets per host class and alert early on journal growth trends.
Related Errors & Cross-Refs
Common alongside /var full alerts, rsyslog backpressure, and app crash loops.
Related tutorial: View the step-by-step tutorial for debian-12.
View all debian-12 tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
systemd-journald.conf manual and Debian logging architecture references.
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.
