diff options
| author | Dave Chinner <dchinner@redhat.com> | 2010-07-23 10:49:41 (GMT) |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2010-07-23 10:50:55 (GMT) |
| commit | aa32a796389bedbcf1c7714385b18714a0743810 (patch) | |
| tree | e94971744e7ceb5585cb04f0ae41d6c3e46a0508 | |
| parent | 43d2932d88e4ab776dd388c20b003ebd5e1d1f1f (diff) | |
| download | linux-aa32a796389bedbcf1c7714385b18714a0743810.tar.xz | |
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>
| -rw-r--r-- | fs/ext3/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/ext3/Kconfig b/fs/ext3/Kconfig index 522b154..e8c6ba0 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 |