Bug 947175

Summary: system.journal reported corrupted after a reboot
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: johannbg, lnykryn, metherid, mschmidt, msekleta, notting, pedrogfrancisco, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-201-2.fc18.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-16 03:00:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2013-04-01 19:05:56 UTC
Description of problem:

After a clean reboot I found the following in dmesg output

systemd-journald[197]: File /var/log/journal/58f04c45f42a2d1e2e56229b89675900/system.journal corrupted or uncleanly shut down, renaming and replacing.

Eh? Renaming to what and why it is possibly corrupted?

Version-Release number of selected component (if applicable):
systemd-199-1.fc20

How reproducible:
Hard to tell.  Next two reboots, performed in exactly the same way, did not make this message to reappear.  It also does not seem to be logged anywhere so if not noticed in dmesg output it is gone.

Additional info:
I noticed that accidentally when checking for other things.  There is a number of files in /var/log/journal/58f04c45f42a2d1e2e56229b89675900/ but these do not seem to be related to this corruption notice.  journalctl appear to be able to read entries earlier than this incident.

Comment 1 Michal Schmidt 2013-04-03 10:07:22 UTC
A possible cause of this has been fixed by Lennart:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=aaf7eb81be912e7bed939f31e3bc4c631b2552b3

Comment 2 Michal Jaegermann 2013-04-03 15:27:25 UTC
(In reply to comment #1)
> A possible cause of this has been fixed by Lennart:
I was trying to watch for this and so far did not see another occurence.  OTOH the possible fix shows that this is a kind of a race so that is so surprising.

Comment 3 Fedora Update System 2013-04-10 20:16:01 UTC
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1

Comment 4 Fedora Update System 2013-04-11 23:29:10 UTC
Package systemd-201-2.fc18.2:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-04-16 00:03:48 UTC
Package systemd-201-2.fc18.4:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.4
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-04-18 02:41:23 UTC
Package systemd-201-2.fc18.5:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-05-07 13:43:23 UTC
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6

Comment 8 Fedora Update System 2013-05-09 10:04:53 UTC
Package systemd-201-2.fc18.6:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-05-16 03:00:31 UTC
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Pedro Francisco 2013-07-14 00:55:09 UTC
The original bug was submitted for FC20, the updated packages were submitted to FC18 and I'm seeing this message on my FC19 system.

systemd-204-9.fc19.i686

$ sudo yum install systemd --enablerepo=updates-testing
(...)
Package systemd-204-9.fc19.i686 already installed and latest version

Shouldn't FC19 and FC20 packages also be updated?