User: Password:
|
|
Subscribe / Log in / New account

2.6.36 merge window: the sequel

2.6.36 merge window: the sequel

Posted Aug 19, 2010 9:33 UTC (Thu) by renox (subscriber, #23785)
Parent article: 2.6.36 merge window: the sequel

>> The ext3 filesystem, once again, defaults to the (safer) "ordered" mode at mount time. This reverses the change (to "writeback" mode) made in 2009, which was typically overridden by distributions. <<

Is-there an interesting inside story with this?
This kind of change of the default setting looks really amateurish for an external point of view..


(Log in to post comments)

Re: ext3: default to ordered mode

Posted Aug 19, 2010 11:45 UTC (Thu) by cladisch (✭ supporter ✭, #50193) [Link]

From this thread:
Ok, so now I know *why* that one filesystem got busted - I built a
kernel without CONFIG_EXT3_DEFAULTS_TO_ORDERED set and it got a
forced reboot (echo b > proc/sysrq-trigger). That'll teach me for
trying to reproduce bugs Andrew is tripping over with his config
files.
Quite frankly, data=writeback mode for ext3 is a dangerous,
dangerous configuration to run by default. IMO, it shouldn't be the
default. Patch below.
Jan's changelog:
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.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds