linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Theodore Tso <tytso@mit.edu>, Valerie Aurora <vaurora@redhat.com>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	Eric Sandeen <esa
Subject: ext3 default journal mode
Date: Sun, 19 Jul 2009 22:50:49 -0400	[thread overview]
Message-ID: <4A63DB89.2060306@redhat.com> (raw)


Now that we have put some some distance between us and the mega-thread, I think 
that it is time to put some sanity back into the ext3 journal mode options.

My preference is to revert the default back to ordered mode or (if Chris is 
ready) back to guarded mode.

As I mentioned in an earlier email, I think *every* distribution undid this 
default back to ordered mode.

Do any of us who deal in file systems really think that writeback is a 
reasonable default for unsophisticated users or non-FS experts (like those in 
the embedded space) who rely on KCONFIG to get a sense of a debate that they missed?

Failing that, I would like to at very least put sane text in the KCONFIG option.

Something like the following:

diff --git a/fs/ext3/Kconfig b/fs/ext3/Kconfig
index fb3c1a2..4057730 100644
--- a/fs/ext3/Kconfig
+++ b/fs/ext3/Kconfig
@@ -36,16 +36,19 @@ config EXT3_DEFAULTS_TO_ORDERED
           mode, and the journal capability allowed it, ext3 used to
           historically default to 'data=ordered'.

-         That was a rather unfortunate choice, because it leads to all
-         kinds of latency problems, and the 'data=writeback' mode is more
-         appropriate these days.
+         Data ordered mode is the mode used by most distributions, but can
+         introduce latency problems in some workloads, especially if you have
+         a very low latency device.

-         You should probably always answer 'n' here, and if you really
-         want to use 'data=ordered' mode, set it in the filesystem itself
-         with 'tune2fs -o journal_data_ordered'.
+         The current default mode is data writeback mode which favors latency but
+         is more prone to corruption after crashes and power failures and will
+         expose deleted data after a crash to newly allocated files.

-         But if you really want to enable the legacy default, you can do
-         so by answering 'y' to this question.
+         If you have been historically happy with ext3's performance, data ordered
+         mode will be a safe choice and you should answer "y" here.
+
+         If you understand the reliability and data privacy issues of data 
writeback
+         mode and are willing to make that trade off, answer "n".



             reply	other threads:[~2009-07-20  2:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  2:50 Ric Wheeler [this message]
2009-07-20 14:18 ` ext3 default journal mode Chris Mason
2009-07-20 14:32   ` Ric Wheeler
2009-07-20 21:29 ` Theodore Tso
2009-07-20 21:33   ` Ric Wheeler
2009-07-20 23:04   ` Valerie Aurora
2009-07-20 23:36     ` Andreas Dilger
2009-07-21 17:44       ` Valerie Aurora
2009-07-21  2:00     ` Theodore Tso
2009-07-21 17:44       ` Valerie Aurora
2009-07-23 13:14         ` Ric Wheeler
2009-07-20 22:58 ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A63DB89.2060306@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=tytso@mit.edu \
    --cc=vaurora@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).