All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jon Hedlund <JH_ML@invtools.com>,
	sct@redhat.com, akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: 2.2 kernel - Ext3 & Raid patches
Date: Wed, 22 May 2002 11:16:10 +0100	[thread overview]
Message-ID: <20020522111610.A3180@redhat.com> (raw)
In-Reply-To: <3CEA7866.23557.390B7FFC@localhost> <20020522012133.GE13211@turbolinux.com>

Hi,

On Tue, May 21, 2002 at 07:21:33PM -0600, Andreas Dilger wrote:
> On May 21, 2002  16:40 -0500, Jon Hedlund wrote:
> > Last September Stephan told someone on the linux-kernel list that 
> > Ext3 and Raid 1 didn't work together on the 2.2 kernel. 
> > Has this been fixed or have I just been lucky?
> 
> You've just been lucky.  I forget the exact scenario, but it is
> something like if journal replay is happening while the RAID is being 
> reconstructed after a crash you can get garbage written to your disk.

Right --- the raid resync code in 2.2 uses the normal buffer cache,
which results in writes being scheduled for clean buffers, behind
ext3's back.  That's not allowed --- it violates the write ordering
requirements that make ext3 work, and trips up debugging assert
failures in the ext3 write checking code.

You might get away with it, but a raid resync on ext3 on 2.2 is
basically not safe.  If you wait until after the resync before
mounting the ext3 filesystem, you'll be OK.

It should work on 2.4.

Cheers,
 Stephen

  reply	other threads:[~2002-05-22 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 21:40 2.2 kernel - Ext3 & Raid patches Jon Hedlund
2002-05-22  1:21 ` Andreas Dilger
2002-05-22 10:16   ` Stephen C. Tweedie [this message]
2002-05-23  1:11 ` Mike Fedyk
2002-05-23  7:02   ` Tomas Szepe
2002-05-23  7:03     ` David S. Miller
2002-05-23  7:21       ` Tomas Szepe
2002-05-23  8:42       ` Tomas Szepe
2002-05-23  8:49   ` Stephen C. Tweedie
2002-05-23 14:52     ` Herman Oosthuysen
2002-05-23 22:25       ` Stephen C. Tweedie

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=20020522111610.A3180@redhat.com \
    --to=sct@redhat.com \
    --cc=JH_ML@invtools.com \
    --cc=akpm@zip.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.