From: Eric Sandeen <sandeen@redhat.com>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.35-r5 ext3 corruptions
Date: Wed, 21 Jul 2010 09:01:49 -0500 [thread overview]
Message-ID: <4C46FDCD.9010007@redhat.com> (raw)
In-Reply-To: <20100721140758.68ca16ab@debian>
Török Edwin wrote:
> On Wed, 21 Jul 2010 16:32:22 +1000
> Dave Chinner <david@fromorbit.com> wrote:
...
>> Quite frankly, data=writeback mode for ext3 is a dangerous,
>> dangerous configuration to run by default. IMO, it shouldn't be the
>> default. Patch below.
>
> Hi,
>
> I don't see CONFIG_EXT3_DEFAULTS_TO_ORDERED in my .config at all.
> What I have in my .config is:
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_USE_FOR_EXT23=y
> CONFIG_EXT4_FS_XATTR=y
>
> So what is the equivalent of that config option for ext4 used as ext3
> driver?
There is none AFAICT, just an artifact of the twisting option-paths of
extN, I guess. :)
Good news is you should get something sane, and -not- default to writeback
with your config.
-Eric
> Best regards,
> --Edwin
--
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:[~2010-07-21 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 10:57 2.6.35-r5 ext3 corruptions Dave Chinner
2010-07-15 11:26 ` Dave Chinner
2010-07-15 18:23 ` Josef Bacik
2010-07-15 20:14 ` Johannes Hirte
2010-07-19 22:45 ` Dave Chinner
2010-07-21 6:32 ` Dave Chinner
2010-07-21 11:07 ` Török Edwin
2010-07-21 14:01 ` Eric Sandeen [this message]
2010-07-21 13:55 ` Eric Sandeen
2010-07-23 10:43 ` Jan Kara
2010-07-23 10:53 ` Jan Kara
2010-07-23 10:55 ` Dave Chinner
2010-07-23 10:58 ` Christoph Hellwig
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=4C46FDCD.9010007@redhat.com \
--to=sandeen@redhat.com \
--cc=david@fromorbit.com \
--cc=edwintorok@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).