| commit | aa32a796389bedbcf1c7714385b18714a0743810 | |
| author | Dave Chinner <dchinner@redhat.com> | |
| Fri, 23 Jul 2010 10:49:41 +0000 (23 12:49 +0200) | ||
| committer | Jan Kara <jack@suse.cz> | |
| Fri, 23 Jul 2010 10:50:55 +0000 (23 12:50 +0200) | ||
| tree | e94971744e7ceb5585cb04f0ae41d6c3e46a0508 | treesnapshot (tar.gz zip) |
| parent | 43d2932d88e4ab776dd388c20b003ebd5e1d1f1f | commitdiff |
ext3: default to ordered mode
data=writeback mode is dangerous as it leads to higher data loss and stale data
exposure when systems crash. It should not be the default, especially when all
major distros ensure their ext3 filesystems default to ordered mode. Change the
default mode to the safer data=ordered mode, because we should be caring far
more about avoiding stale data exposure than performance.
CC: linux-ext4@vger.kernel.org
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Acked-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>
data=writeback mode is dangerous as it leads to higher data loss and stale data
exposure when systems crash. It should not be the default, especially when all
major distros ensure their ext3 filesystems default to ordered mode. Change the
default mode to the safer data=ordered mode, because we should be caring far
more about avoiding stale data exposure than performance.
CC: linux-ext4@vger.kernel.org
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Acked-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>
| fs/ext3/Kconfig | diffblobblamehistory |