All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Jon Hedlund <JH_ML@invtools.com>
Cc: sct@redhat.com, akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: 2.2 kernel - Ext3 & Raid patches
Date: Tue, 21 May 2002 19:21:33 -0600	[thread overview]
Message-ID: <20020522012133.GE13211@turbolinux.com> (raw)
In-Reply-To: <3CEA7866.23557.390B7FFC@localhost>

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.

> Three times in the last 9 months one of the drives reported errors 
> and dropped offline, each time I have fdisked the bad drive, 
> formatted it, fsck'ed it and found no problems, fdisked it again, and 
> raidhotadd'ed it back in and it restored the array without problems.

This is probably a matter of block remapping replacing bad sectors when
you try to write to it.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-05-22  1:23 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 [this message]
2002-05-22 10:16   ` Stephen C. Tweedie
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=20020522012133.GE13211@turbolinux.com \
    --to=adilger@clusterfs.com \
    --cc=JH_ML@invtools.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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.