Skip to main content

Journal log size Opimization

/var/log/journal is too high


You can quickly clear space by running sudo journalctl --vacuum-size=100M to limit the size of your system logs. [1]
Immediate Cleanup
  • Check current size: Run journalctl --disk-usage to see how much space the logs take.
  • Reduce by size: Run sudo journalctl --vacuum-size=500M to shrink the logs down to 500 megabytes (or another size like 1G).
  • Reduce by time: Run sudo journalctl --vacuum-time=2weeks to delete logs older than a specific timeframe. [1, 2, 3]
Permanent Fix
  • Open config file: Edit /etc/systemd/journald.conf using a text editor with root privileges (like sudo nano /etc/systemd/journald.conf).
  • Set maximum limits: Find and uncomment (remove the # at the start of) lines like SystemMaxUse=500M or SystemMaxFileSize=50M to
  • Linux Mint

    SOLVED: var/log is large and keeps growing
    ... /var/log/lightdm 4.0K /var/log/mintsystem.log 4.0K /var/

  • Debian forums

    [Solved] How to manage the size of /var/log/journal
    My system runs headless and I have only 782 packages install...

  • SiteLint

    How do I clear a big /var/log/journal folder? - SiteLint
    Let's then delete old log files from the /var/log/journal fo...
Show all

How big is reasonable size for journal ?








For most personal computers and standard servers, a reasonable size for the systemd journal is between 500MB and 4GB.
Recommended Settings By System Type
  • Desktop / Personal PC (500MB – 1GB): Enough for daily troubleshooting without wasting SSD space.
  • Standard Web/App Server (1GB – 2GB): Retains weeks of operational history for debugging.
  • Production / High-Traffic Server (4GB – 10GB): Necessary if you log heavy application traffic locally.
  • Containers / Microservices (50MB – 100MB): Keep it minimal since logs should stream to an external aggregator.
Factors to Consider
  • Disk Capacity: A safe rule of thumb is to limit your journal to 10% of your total partition size (systemd's default behavior) or caps at 4GB, whichever is smaller.
  • Log Rotation Frequency: If your system generates 500MB of logs a day, a 1GB limit only gives you 2 days of history.
  • External Forwarding: If you send logs to a central server (like Elasticsearch or Datadog), you can safely set the local journal size much lower.
If you want to fine-tune this, let me know:
  • Is this for a personal PC or a server?
  • What is the total storage capacity of your drive?
I can help you calculate the exact configuration values to use.
AI responses may include mistakes. Learn more


For a personal server with an i5 processor and 8GB of RAM, a reasonable journal size is 1GB to 2GB. This provides months of troubleshooting history without wasting valuable disk space.
Recommended Configuration
To set this up permanently, open your configuration file:
sudo nano /etc/systemd/journald.conf
Uncomment and update the following lines to these recommended values:
  • SystemMaxUse=2G (Caps total disk space used by logs)
  • SystemMaxFileSize=200M (Splits logs into smaller, easier-to-read files)
  • RuntimeMaxUse=200M (Caps log memory usage to protect your 8GB RAM)
Save the file and apply the changes instantly by running:
sudo systemctl restart systemd-journald
Back to top