On Mon, Jul 20, 2009 at 05:29:04PM -0400, Theodore Tso wrote:
> Here's a revised proposal for the KCONFIG text.
>
> Hopefully this is balanced about the two sides of the issue, without
> explicitly advocating for one choice versus another.
>
> What do people think?
I think it's extremely accurate and detailed, but too long - people's
brains turn off after about the 15th line or so. Here's an attempt to
distill your description down and refer out to another document (which
one?) for people who want to learn more.
(Sorry for the whitespace damage.)
-VAL
config EXT3_DEFAULTS_TO_ORDERED
bool "Default to 'data=ordered' in ext3"
depends on EXT3_FS
help
If the mount options for an ext3 filesystem do not
include a journal mode, mount it in "data=ordered" mode.
The journal mode options for ext3 have different tradeoffs
between when data is guaranteed to be on disk and
performance. Many applications assume "data=ordered"
semantics and may lose, destroy, or reveal other user's data
in other journal modes. However, "data=ordered" mode can
also result in major performance problems, including long
delays before an fsync() call returns. For details, see:
XXX some document
Use "data=ordered" mode unless you know it is causing a
performance problem for your workload.
If you are unsure, say 'Y'.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
