Show your journalsize ;)

journalctl --disk-usage

mine:

[joekamprad@FrameWork13]$~: journalctl --disk-usage
Archived and active journals take up 746.1M in the file system.

curious as of reading here:
https://wiki.archlinux.org/title/Systemd/Journal#Journal_size_limit not clear on how exactly it is set by default..

❯ journalctl --disk-usage
Archived and active journals take up 318.9M in the file system.
❯
❯ journalctl --disk-usage
Archived and active journals take up 347.6M in the file system.

~ 
❯ 

I limit mine.

Stagger_Lee>> journalctl --disk-usage
Archived and active journals take up 51.5M in the file system.
>>> journalctl --disk-usage                                                                                  
Archived and active journals take up 969.9M in the file system.

I probably should limit mine

# SystemMaxUse = total amount of disk space the journal can use
# Default is 10% of total filesystem size
#
# SystemMaxFileSize = max size an individual journal file can be
# Default is one-eighth of the value configured via SystemMaxUse=
╰─❯ journalctl --disk-usage


Archived and active journals take up 2G in the file system.
╰─❯  journalctl --disk-usage
Archived and active journals take up 472.5M in the file system.

$ journalctl --disk-usage
Archived and active journals take up 1.1G in the file system.

Darn, might need to clean up…

Wonder if I should set up an auto-vacuum crontab entry? :thinking: (I typically use --vacuum-time=2w when I’m not forgetting.)

The Arch wiki links to the explanation how to set it by default?

You people and your tiny little journals. :cowboy_hat_face:

Archived and active journals take up 1.6G in the file system.

Those are rookie numbers :stuck_out_tongue:

journalctl --disk-usage
Archived and active journals take up 56M in the file system.

I capped mine via the config edit to 150M, and 2 weeks of logs is usually always less than that for me, the below is around 2 weeks worth, saves having to vacuum all the time to 2 weeks.

journalctl --disk-usage
Archived and active journals take up 136M in the file system.

45M but I am on a setup that’s less than a month old, on my old one it owuldn’t have been much biger though cuz I clear out old logs regularly to save disk space.

I must have set mine at some point as this is about a 5 year old install.
journalctl --disk-usage
Archived and active journals take up 46.2M in the file system.

Don’t worry, boys! I’ve got room to spare.

journalctl --disk-usage    
Archived and active journals take up 1G in the file system.

I was reading wiki.. and tried to find out why it mentioned that in case it’s grown big it could slow down boot on systemd-boot. Also wondering if a system has some bad implemented hardware that spams the journal .. but every one here have normal size.. except one person

Let me add the output for some long run installs of mine.

 thefrog@thepad:~🖝  journalctl --disk-usage
Archived and active journals take up 503.8M in the file system.

Screenshot_20250701_201810

awk -F “[” ‘NR==1 {print $2;}’ /var/log/pacman.log

2025-07-01_20-21