| commit | b71a005bac02d0f68ba2d93f47cd58afcd563149 | |
| author | Theodore Ts'o <tytso@mit.edu> | |
| Sun, 15 Nov 2009 20:31:37 +0000 (15 15:31 -0500) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 18 Dec 2009 22:03:56 +0000 (18 14:03 -0800) | ||
| tree | 0a0571bb6bf9f92f255872ca9fef37acc6e280cd | treesnapshot (tar.gz zip) |
| parent | 943e167cb3e8fb191894bde8a4a75db78531a7c8 | commitdiff |
jbd2: don't wipe the journal on a failed journal checksum
commit e6a47428de84e19fda52f21ab73fde2906c40d09 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>
commit e6a47428de84e19fda52f21ab73fde2906c40d09 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>
| fs/jbd2/journal.c | diffblobblamehistory |