$ journalctl -b -u systemd-journald.service -n 1
-- Logs begin at Sat 2018-09-29 05:03:28 CEST, end at Thu 2019-03-21 18:18:38 CET. --
Mar 20 13:32:03 debby2017 systemd-journald[699]: System journal (/var/log/journal/f8b692c8bb791fe2804f3d5a5905148b) is 1.8G, max 1.8G, 0B free.
$ journalctl --disk-usage
Archived and active journals take up 1.8G in the file system.
However, with systemd-journald persistence enabled, and classic logging daemons not removed (and still logging) on upgrades, you can end up with much data stored in /var/log, a lot more than there used to be in the past, which could cause problems, also (but not only) if combined with bug 1785321.
Not breached here:
$ journalctl -b -u systemd- journald. service -n 1 journald[ 699]: System journal (/var/log/ journal/ f8b692c8bb791fe 2804f3d5a590514 8b) is 1.8G, max 1.8G, 0B free.
-- Logs begin at Sat 2018-09-29 05:03:28 CEST, end at Thu 2019-03-21 18:18:38 CET. --
Mar 20 13:32:03 debby2017 systemd-
$ journalctl --disk-usage
Archived and active journals take up 1.8G in the file system.
However, with systemd-journald persistence enabled, and classic logging daemons not removed (and still logging) on upgrades, you can end up with much data stored in /var/log, a lot more than there used to be in the past, which could cause problems, also (but not only) if combined with bug 1785321.