Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when rotating the system journal file due to corruption, log that fact to the journal once we are done with it, not just kmsg #16173

Open
cmurf opened this issue Jun 13, 2020 · 0 comments
Labels

Comments

@cmurf
Copy link
Contributor

cmurf commented Jun 13, 2020

systemd version the issue has been seen with

systemd-245.4-1.fc32.x86_64

Used distribution

Fedora Workstation 32

Expected behaviour you didn't see

This kernel message should be in the systemd-journal also.

$ dmesg | grep corrupt
[    4.989946] systemd-journald[566]: File /var/log/journal/2d2b0efcba8442caaf742548b8b2e6ef/system.journal corrupted or uncleanly shut down, renaming and replacing.
$ 

Unexpected behaviour you saw

Journal corruption message is not in the journal.

$ sudo journalctl -b | grep corrupt
Jun 13 13:51:31 localhost.localdomain systemd-fsck[683]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
$

Steps to reproduce the problem

  1. Boot to login window then force power off (VM or baremetal)
  2. Boot again.
  3. Compare dmesg vs sudo journalctl for 'corrupt' messages.
    Reproduces 100% of the time.
@poettering poettering changed the title missing kernel messages from sd-journal when rotating the system journal file due to corruption, log that fact to the journal once we are done with it, not just kmsg Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants