<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - journal gets corrupted without crash" href="https://bugs.freedesktop.org/show_bug.cgi?id=65235#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - journal gets corrupted without crash" href="https://bugs.freedesktop.org/show_bug.cgi?id=65235">bug 65235</a> from <a class="email" href="mailto:george@chinilu.com" title="George Mitchell <george@chinilu.com>"> George Mitchell</a> <pre>Very interesting. This is exactly the sort of corruptions I am seeing in my journal data. I have to systems running multiboot on the same hardware. One is a very basic Mageia 3 64bit system running on ext4. It has zero problem with journal corruptions. The other is my main system, a 32bit Mageia 3 system running on 64bit Intel hardware. The file system is exclusively btrfs raid 1 configuration. On this system I get a constant flow of corruptions that look exactly like what Hussam is seeing. The corruptions typically occur 89-95% into the verify scan. What is interesting is that I am not seeing any problem with the actual logs, only with the verifies. But I am finding that once these corruptions accumulate to a certain point the journal logging system itself dies. I have had that happen once already and was only able to restore it by cleaning out the old journal files. Since I can't trust the journal on this system, I am running rsyslog as a backup.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>