From: Ric Wheeler <rwheeler@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Stephen C. Tweedie" <sct@redhat.com>,
Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
Eric Sandeen <esandeen@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: default ext3 journal mode - time to poke at this again?
Date: Mon, 20 Jul 2009 15:25:00 -0400 [thread overview]
Message-ID: <4A64C48C.8000504@redhat.com> (raw)
In-Reply-To: <20090720185731.GA9002@atrey.karlin.mff.cuni.cz>
On 07/20/2009 02:57 PM, Jan Kara wrote:
> Hi,
>
>
>> At the linux symposium this week, some of us were wondering when it
>> would be safe to try and default ext3's default journal mode back to
>> sanity given that all (?) distros immediately reverted the default to
>> data writeback mode.
>>
> Well, at least SUSE still uses data=ordered,barrier as a default (and
> I personally think this is the right thing to do). Hmm, maybe you've
> meant this and just wrote it otherwise given your paragraph below ;)
>
Definitely what I meant to post - Fedora and RHEL both use ordered mode
as a default as well. Not many fs developers are fans of data writeback
mode as far as I can tell...
>
>> Failing that, can we at least clean up the config option description to
>> properly give the normal users a non-bogus, technical description of the
>> trade off ?
>>
> Yes, I'm all for it. Will you try to write up something or should I?
>
> Honza
>
I posted something (from rwheeler@redhat.com) earlier today and we had a
discussion about this on the ext4 call. I think that Ted will try to
update the text that I proposed over the next couple of days.
I think that Chris will be reposting his data guarded mode patches soon
as well, so we might be able to move forward quickly :-)
ric
prev parent reply other threads:[~2009-07-20 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 12:54 default ext3 journal mode - time to poke at this again? Ric Wheeler
2009-07-20 18:57 ` Jan Kara
2009-07-20 19:25 ` Ric Wheeler [this message]
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=4A64C48C.8000504@redhat.com \
--to=rwheeler@redhat.com \
--cc=adilger@sun.com \
--cc=esandeen@redhat.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).