Antw: [EXT] kernel messages not making it to journal

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> Chris Murphy <lists@xxxxxxxxxxxxxxxxx> schrieb am 02.06.2020 um 03:11 in
Nachricht
<24912_1591060304_5ED5A750_24912_140_1_CAJCQCtS0r0O9KdvGpV_B9ku5-ure+nGOpRrYYm=V
ygGps1YNg@xxxxxxxxxxxxxx>:
> dmesg shows this:
> 
> [   22.947118] systemd‑journald[629]: File
> /var/log/journal/26336922e1044e80ae4bd42e1d6b9099/user‑1000.journal
> corrupted or uncleanly shut down, renaming and replacing.
> [   22.953883] systemd‑journald[629]: Creating journal file
> /var/log/journal/26336922e1044e80ae4bd42e1d6b9099/user‑1000.journal on
> a btrfs file system, and copy‑on‑write is e

I saw a similar message for some "secure boot stick" when the journal daemon
crashed during boot with syssegv...

> 
> But journalctl does not show it at all. Seems like it might be a bug,
> I expect it to be recorded in the journal, not only found in dmesg.
> 
> systemd‑245.4‑1.fc32.x86_64
> 
> Thanks,
> 
> ‑‑ 
> Chris Murphy
> _______________________________________________
> systemd‑devel mailing list
> systemd‑devel@xxxxxxxxxxxxxxxxxxxxx 
> https://lists.freedesktop.org/mailman/listinfo/systemd‑devel 



_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel