Logging & Journald

Stop watching journald eat your disk space alive

🧩 The Challenge

Dealing with a full root partition because journald decided to hoard three years of logs is a special kind of Monday morning headache. Nobody tells you that the default retention settings are basically “store everything until the server dies.”

💡 The Fix

You can clamp down on how much storage the journal consumes or how long it hangs onto old entries. It’s the easiest way to prevent a production outage caused by log bloat.

journalctl --vacuum-time=7d
journalctl --vacuum-size=500M

⚙️ Why It Works

These commands force systemd to prune the binary log files based on time or total disk usage, which immediately frees up space. You can also edit /etc/systemd/journald.conf to set these limits permanently so you never have to think about it again.

🚀 Pro-Tip: Use SystemMaxUse in your config file to set a hard cap so the logs never exceed a specific footprint.

Linux Tips & Tricks | © ngelinux.com | 10/6/2026