[systemd-bugs] [Bug 90074] New: journalctl does not show log past an invalid entry
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Apr 17 07:02:38 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90074
Bug ID: 90074
Summary: journalctl does not show log past an invalid entry
Product: systemd
Version: unspecified
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: zebul666 at hotmail.com
QA Contact: systemd-bugs at lists.freedesktop.org
>From what I understand, journalctl is supposed to show all the log in
/var/log/journal/<machine-uuid>/system*.journal ?
But I have a file that is reported corrupted by journalctl --verify with an
invalid entry (most likely the last one) caused by a hard-reboot without fsck
# journalctl --verify
[...]
8a8ef0: invalid entry item (13/22 offset: 000000
8a8ef0: invalid object contents: Bad message
File corruption detected at
/var/log/journal/<mymachine-uuid>/system at 000xxxxxxxxx-xxxxxxxxxxxxxx.journal~:8a8ef0
(of 16777216 bytes, 54%).
FAIL:
/var/log/journal/<mymachine-uuid>/system at 000xxxxxxxxxxxx-xxxxxxxxxx.journal~
(Bad message)
[...]
and journalctl does not show log past/after that invalid entry i.e. it shows
log from the first 2 system@*.journal~ files, but no log from the other files,
where the last shown log file is from the one corrupted.
I have to access each file individualy with journalctl --file=<name-of-file>
using systemd 219 on ubuntu 15.04 beta 2
a similar story on archlinux forum
https://bbs.archlinux.org/viewtopic.php?id=188157
p.s: where is the tool to repair corrupted log ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150417/5b665c33/attachment.html>
More information about the systemd-bugs
mailing list