Safe to Delete

Linux Systemd Journalctl Logs Folder (/var/log/journal)

Quick Answer: /var/log/journal stores binary system logs collected by systemd-journald. Vacuuming old journal logs is 100% safe via journalctl.

Bottom Line: It is 100% safe to vacuum and delete old systemd journal logs. Running journalctl --vacuum-time=7d or setting SystemMaxUse will NOT break Linux services or system startup.


What is the /var/log/journal Folder?

Located at /var/log/journal/ (or /run/log/journal/) on Linux distributions using systemd (Ubuntu, Debian, Fedora, Arch, RHEL), this folder is managed by systemd-journald.

Systemd collects binary event logs from the Linux kernel, system daemons, Nginx, Docker, and user services. Unlike traditional text log files in /var/log, journalctl logs are stored in indexed binary .journal files.

By default, systemd-journald is configured to use up to 10% of total filesystem capacity, easily consuming 5 GB to 20 GB+ of root partition storage.


Can You Delete Journalctl Logs?

✅ Yes, it is completely safe to vacuum.

  • No server risk: Live system services stay 100% operational.
  • Official systemd commands: journalctl includes built-in commands specifically designed to purge old logs safely.

How to Safely Clean Up Systemd Journal Logs

  1. Open your Linux terminal.
  2. Vacuum journal logs older than 7 days:
    sudo journalctl --vacuum-time=7d

Method 2: Limit Journal Log Storage Size

To permanently cap journal log disk usage to 1 GB:

  1. Vacuum logs to 1 GB immediately:
    sudo journalctl --vacuum-size=1G
  2. Edit /etc/systemd/journald.conf:
    [Journal]
    SystemMaxUse=1G
  3. Restart systemd-journald:
    sudo systemctl restart systemd-journald

Discussion

Loading authentication...

Related in linux

Linux Audit Framework Log Directory (/var/log/audit)

The Linux auditd service records security events, file access traces, and user commands in /var/log/audit. Learn how to clean auditd log files safely.

Safe to Delete

Fail2ban Ban History Database (/var/lib/fail2ban/fail2ban.sqlite3)

Fail2ban intrusion prevention daemon logs banned IP addresses and SSH brute-force attempts in fail2ban.sqlite3. Clearing Fail2ban database is safe.

Safe to Delete

GNOME Desktop File Indexer Database (~/.local/share/tracker/data)

GNOME Tracker caches desktop search index databases. Resetting the tracker database is safe.

Safe to Delete
Back to all files