Theodore Ts'o b71a005bac jbd2: don't wipe the journal on a failed journal checksum ... commit e6a47428de upstream. If there is a failed journal checksum, don't reset the journal. This allows for userspace programs to decide how to recover from this situation. It may be that ignoring the journal checksum failure might be a better way of recovering the file system. Once we add per-block checksums, we can definitely do better. Until then, a system administrator can try backing up the file system image (or taking a snapshot) and and trying to determine experimentally whether ignoring the checksum failure or aborting the journal replay results in less data loss. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>		2009-12-18 14:03:56 -08:00
..
checkpoint.c	jbd2: Use tracepoints for history file	2009-09-30 00:32:06 -04:00
commit.c	jbd2: Add ENOMEM checking in and for jbd2_journal_write_metadata_buffer()	2009-12-14 09:45:10 -08:00
journal.c	jbd2: don't wipe the journal on a failed journal checksum	2009-12-18 14:03:56 -08:00
Kconfig	fs/Kconfig: move ext2, ext3, ext4, JBD, JBD2 out	2008-10-20 11:43:59 -07:00
Makefile
recovery.c	jbd2: fix error handling for checkpoint io	2008-10-10 20:29:13 -04:00
revoke.c	jbd2: use SWRITE_SYNC_PLUG when writing synchronous revoke records	2009-04-14 07:50:56 -04:00
transaction.c	jbd2: Annotate transaction start also for jbd2_journal_restart()	2009-08-17 21:23:17 -04:00