http://bugzilla.kernel.org/show_bug.cgi?id=14354 --- Comment #174 from Eric Sandeen <sandeen@xxxxxxxxxx> 2009-11-03 23:39:40 --- Tidbit; after turning on checksums but disabling any action on a mismatch, and adding a little instrumentation, I got something like: checksum error 1293235, (not) breaking normal scan finish, setting end_transaction to 1293246 (fs/jbd2/recovery.c, 388): do_one_pass: Starting recovery pass 1 (fs/jbd2/recovery.c, 388): do_one_pass: Starting recovery pass 2 (fs/jbd2/recovery.c, 257): jbd2_journal_recover: JBD: recovery, exit status 0, recovered transactions 1293215 to 1293246 IOW, the checksum error was far from the last transaction in the log; it was somewhere in the middle-ish of what needed to be replayed. So this more or less explains the corruption (many transactions were not replayed because recovery was aborted when the bad checksum was found), and it doesn't necessarily point to a problem with the transaction in flight when the power-fail occurred... we had about 10 transactions after that. Hrm. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
