From: Valerie Aurora <vaurora@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Ric Wheeler <rwheeler@redhat.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"Stephen C. Tweedie" <sct@redhat.com>,
Eric Sandeen <esandeen@redhat.com>,
Andreas Dilger <adilger@sun.com>,
Chris Mason <chris.mason@oracle.com>,
Josef Bacik <jbacik@redhat.com>, Mingming Cao <cmm@us.ibm.com>
Subject: Re: ext3 default journal mode
Date: Tue, 21 Jul 2009 13:44:07 -0400 [thread overview]
Message-ID: <20090721174406.GA28383@shell> (raw)
In-Reply-To: <20090721020050.GK2416@mit.edu>
On Mon, Jul 20, 2009 at 10:00:50PM -0400, Theodore Tso wrote:
> On Mon, Jul 20, 2009 at 07:04:03PM -0400, Valerie Aurora wrote:
> >
> > 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.
>
> Fair enough; I've created an external document here:
>
> http://ext4.wiki.kernel.org/index.php/Ext3_Data%3DOrdered_vs_Data%3DWriteback_mode
>
> Comments?
Nice!
> > 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.
>
> Let me give a try at this:
>
> The journal mode options for ext3 have different tradeoffs
> between when data is guaranteed to be on disk and
> performance. The use of "data=writeback" can cause
> unwritten data to appear in files after an system crash or
> power failure, which can be a security issue. However,
> "data=ordered" mode can also result in major performance
> problems, including seconds-long delays before an fsync()
> call returns. For details, see:
>
> http://ext4.wiki.kernel.org/index.php/Ext3_Data%3DOrdered_vs_Data%3DWriteback_mode
>
> 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 and are willing to make
> that trade off, answer "n".
This is great. Ship it!
-VAL
next prev parent reply other threads:[~2009-07-21 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 2:50 ext3 default journal mode Ric Wheeler
2009-07-20 14:18 ` 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 [this message]
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=20090721174406.GA28383@shell \
--to=vaurora@redhat.com \
--cc=adilger@sun.com \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=esandeen@redhat.com \
--cc=jbacik@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=sct@redhat.com \
--cc=tytso@mit.edu \
/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).