23 Jul, 2010
1 commit
-
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
Acked-by: Eric Sandeen
Signed-off-by: Jan Kara
24 Aug, 2009
1 commit
-
The old description for this configuration option was perhaps not
completely balanced in terms of describing the tradeoffs of using a
default of data=writeback vs. data=ordered. Despite the fact that old
description very strongly recomended disabling this feature, all of
the major distributions have elected to preserve the existing 'legacy'
default, which is a strong hint that it perhaps wasn't telling the
whole story.This revised description has been vetted by a number of ext3
developers as being better at informing the user about the tradeoffs
of enabling or disabling this configuration feature.Cc: linux-ext4@vger.kernel.org
Signed-off-by: "Theodore Ts'o"
Signed-off-by: Jan Kara
07 Apr, 2009
1 commit
-
This makes the defautl ext3 data ordering mode (when no explicit
ordering is set) configurable, so as to allow people to default to
'data=writeback' and get the resulting latency improvements.This is a non-issue if a filesystem has been explicitly set to some
ordering (with 'tune2fs').Signed-off-by: Linus Torvalds
21 Oct, 2008
1 commit
-
Use fs/*/Kconfig more, which is good because everything related to one
filesystem is in one place and fs/Kconfig is quite fat.Signed-off-by: Alexey Dobriyan
Signed-off-by: Linus Torvalds
