[systemd-bugs] [Bug 64116] How does one fix journal corruptions?

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64116

--- Comment #1 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
The only way to deal with journal corruptions, currently, is to ignore them:
when a corruption is detected, journald will rename the file to
<something>.journal~, and journalctl will try to do its best reading it.
Actually fixing journal corruptions is a hard job, and it seems unlikely that
it will be implemented in the near future.

Note that the corruption reporting has become more verbose since this bug was
reported, and some "corruptions" that were reported as such are now reported as
unusual, but acceptable events (happened after 204, so the changes are included
in systemd-205).

-- 
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/20130805/2151890b/attachment.html>