Logging & Journald

Stop the journal from drowning your disk

🧩 The Challenge

Dealing with a production server that suddenly hits 100% disk usage because journald went rogue and ballooned to 20 gigabytes is a special kind of nightmare. You end up having to delete files manually like a caveman while services are crashing left and right.

💡 The Fix

You can actually tell journald to cap its storage size so it automatically cleans up old entries before it eats your root partition. It saves you from having to babysit the disk.

journalctl --vacuum-size=500M

⚙️ Why It Works

Running this forces the journal to rotate its files and purge everything until the total size is under the limit you specified. It’s way better than just clearing the whole log when you need space in a pinch.

🚀 Pro-Tip: Throw that command into a daily cron job if you want to keep the logs tight without thinking about it.

Linux Tips & Tricks | © ngelinux.com | 7/13/2026