From: Xiang Wang <xiangw@google.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Andreas Dilger <adilger@sun.com>,
Curt Wohlgemuth <curtw@google.com>, Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: RFC PATCH: ext4 no journal corruption with locale-gen
Date: Thu, 2 Jul 2009 16:27:26 -0700 [thread overview]
Message-ID: <d5ca277e0907021627t77155cdbm4fa34bd87147d60@mail.gmail.com> (raw)
In-Reply-To: <20090701183509.GB31235@skywalker>
On Wed, Jul 1, 2009 at 11:35 AM, Aneesh Kumar
K.V<aneesh.kumar@linux.vnet.ibm.com> wrote:
> On Mon, Jun 22, 2009 at 11:13:27PM +0200, Andreas Dilger wrote:
>> On Jun 22, 2009 09:42 -0700, Curt Wohlgemuth wrote:
>> > I tested the locale-gen example with all combinations of
>> >
>> > data=writeback
>> > data=ordered
>> > data=journal
>> > <no journal at all>
>>
>> On an unrelated note - would it be useful to mount an ext4 filesystem
>> with a journal using "data=none" (or similar) to run without a journal?
>>
>
> I think this is better. I would suggest data=nojournal. That way we can
> check the mount options to figure out whether we are running with
> journal or not. Also i guess this enables us to run without using a
> journal even if mke2fs created a journal for us
We think adding this "data=nojournal" mount option is a very good idea.
To be more specific, after adding this option, the semantics will be:
If mke2fs does not create a journal, then we should use the
"data=nojournal" mount option only.
If mke2fs creates a journal for us, we are allowed to use one of the
following 4 mount options:
data=nojournal
data=writeback
data=ordered
data=journal
We are now working on this patch and will submit it in a couple of weeks.
Meanwhile if Ted could take the most recent patch from Curt to fix the data
corruption problem, that would be great!
Thanks,
Xiang
> -aneesh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-02 23:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 18:48 RFC PATCH: ext4 no journal corruption with locale-gen Curt Wohlgemuth
2009-06-17 23:46 ` Theodore Tso
2009-06-22 16:42 ` Curt Wohlgemuth
2009-06-22 16:56 ` Aneesh Kumar K.V
2009-06-22 17:01 ` Curt Wohlgemuth
2009-06-22 21:13 ` Andreas Dilger
2009-07-01 18:35 ` Aneesh Kumar K.V
2009-07-01 18:44 ` Michael Rubin
2009-07-02 23:27 ` Xiang Wang [this message]
2009-06-29 17:50 ` Curt Wohlgemuth
2009-07-01 18:31 ` Aneesh Kumar K.V
2009-07-06 3:41 ` Theodore Tso
2009-07-06 15:30 ` Aneesh Kumar K.V
2009-07-13 13:05 ` Theodore Tso
2009-07-06 16:21 ` Xiang Wang
2009-07-09 18:30 ` Xiang Wang
2009-07-10 7:28 ` Aneesh Kumar K.V
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=d5ca277e0907021627t77155cdbm4fa34bd87147d60@mail.gmail.com \
--to=xiangw@google.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=curtw@google.com \
--cc=linux-ext4@vger.kernel.org \
--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).