From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Define conflict between ext3 and raid patches against 2.2.19
Date: Wed, 19 Sep 2001 13:38:11 -0700 [thread overview]
Message-ID: <20010919133811.B22773@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20010916155835.C24067@mikef-linux.matchmail.com> <15271.11056.810538.66237@notabene.cse.unsw.edu.au>
In-Reply-To: <15271.11056.810538.66237@notabene.cse.unsw.edu.au>
On Tue, Sep 18, 2001 at 09:08:32PM +1000, Neil Brown wrote:
> On Sunday September 16, mfedyk@matchmail.com wrote:
> > Hi,
> >
> > I'm trying to setup a 2.2 kernel that I can use for comparison to the latest
> > 2.4 kernels I've been testing, but I came accross a little problem with the
> > patches I've been trying to combine.
> >
> > I've already applied:
> > ide.2.2.19.05042001.patch
> > linux-2.2.19.kdb.diff
> > linux-2.2.19.ext3.diff
> >
> > And now I'm trying to apply raid-2.2.19-A1, and I get one reject in
> > include/linux/fs.h.
>
> You should be aware that ext3 (and other journalling filesystems) do
> not work reliably over RAID1 or RAID5 in 2.2. Inparticular, you can
> get problems when the array is rebuilding/resyncing.
>
> But if you only plan to use ext3 with raid0 or linear, you should be
> fine.
>
Can you point me to an archive that describes how to trigger this bug?
Was it in linux-raid or ext3-users or ...?
Mike
next prev parent reply other threads:[~2001-09-19 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 22:58 Define conflict between ext3 and raid patches against 2.2.19 Mike Fedyk
2001-09-16 23:09 ` Lehmann
2001-09-17 1:43 ` Mike Fedyk
2001-09-17 4:42 ` Andreas Dilger
2001-09-18 11:08 ` Neil Brown
2001-09-18 19:24 ` Mike Fedyk
2001-09-19 20:38 ` Mike Fedyk [this message]
2001-09-19 22:35 ` Neil Brown
2001-09-21 13:10 ` Stephen C. Tweedie
2001-09-21 22:44 ` Mike Fedyk
2001-10-01 21:17 ` Hans Reiser
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=20010919133811.B22773@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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