Anybody else able to reproduce this? https://bugzilla.redhat.com/show_bug.cgi?id=1715699
Basically you just boot a Rawhide LiveOS image in a VM with systemd.log_level=debug and then once booted see what you get for
# journalctl -b -o short-monotonic
It should start with 0 seconds, with the first line of what you see in dmesg. For me it's missing everything before 20 seconds. If I don't use the debug switch, it doesn't happen, so it's like the debug option is flooding the journal and it just bails.
OOooh I have a possible suspect!
[liveuser@localhost ~]$ losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 0 1 /LiveOS/rootfs.img 0 512 /dev/loop2 0 0 0 0 /overlay (deleted) 0 512 /dev/loop0 0 0 0 1 /run/initramfs/live/LiveOS/squashfs.img 0 512 [liveuser@localhost ~]$
What is this loop2 /overlay that's been deleted? I wonder if it's possible the journal got flushed there at first, and then it was deleted?
I find it kinda hard to believe I've got more than 16MiB of journal messages just by booting the system, and there are two system journals in /var/log/journal/$MACHINEID/ but that's apparently not everything.
I'm able to reproduce this problem in a VM with Fedora 30 workstation live. I've updated the bug and proposed it as a blocker for violating the logging criterion in basic.