Re: Binary logs? Ugh.
Zbigniew Jedrzejewski-Szmek 2013-08-05 03:08:22 UTC
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.
Lennart Poettering 2014-06-25 09:51:01 UTC
Yupp, journal corruptions result in rotation, and when reading we try to make the best of it. they are nothing we really need to fix hence.
So in a way you're right to say "The way to read a corrupted log is to just run journalctl", because that's the way to read a log, corrupted or not. But in the case of a corrupted log there's data in there that journalctl won't read and that you can't recover. It's much, much easier to recover data from a corrupt text log.
Biting the hand that feeds IT
