summaryrefslogtreecommitdiff
path: root/fs/ext3/Kconfig
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2010-07-23 12:49:41 +0200
committerJan Kara <jack@suse.cz>2010-07-23 12:50:55 +0200
commitaa32a796389bedbcf1c7714385b18714a0743810 (patch)
treee94971744e7ceb5585cb04f0ae41d6c3e46a0508 /fs/ext3/Kconfig
parent43d2932d88e4ab776dd388c20b003ebd5e1d1f1f (diff)
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>
Diffstat (limited to 'fs/ext3/Kconfig')
-rw-r--r--fs/ext3/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/ext3/Kconfig b/fs/ext3/Kconfig
index 522b15498f45..e8c6ba0e4a3e 100644
--- a/fs/ext3/Kconfig
+++ b/fs/ext3/Kconfig
@@ -31,6 +31,7 @@ config EXT3_FS
config EXT3_DEFAULTS_TO_ORDERED
bool "Default to 'data=ordered' in ext3"
depends on EXT3_FS
+ default y
help
The journal mode options for ext3 have different tradeoffs
between when data is guaranteed to be on disk and