From: Stephen Frost <sfrost@snowman.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
Bernd Eckenfels <ecki@lina.inka.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RAID-5 design bug (or misfeature)
Date: Mon, 30 May 2005 09:23:28 -0400 [thread overview]
Message-ID: <20050530132328.GA30011@ns.snowman.net> (raw)
In-Reply-To: <1117454144.2685.174.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> On Llu, 2005-05-30 at 03:47, Mikulas Patocka wrote:
> > > In article <Pine.LNX.4.58.0505300043540.5305@artax.karlin.mff.cuni.cz> you wrote:
> > > > I think Linux should stop accessing all disks in RAID-5 array if two disks
> > > > fail and not write "this array is dead" in superblocks on remaining disks,
> > > > efficiently destroying the whole array.
>
> It discovered the disks had failed because they had outstanding I/O that
> failed to complete and errorred. At that point your stripes *are*
> inconsistent. If it didn't mark them as failed then you wouldn't know it
> was corrupted after a power restore. You can then clean it fsck it,
> restore it, use mdadm as appropriate to restore the volume and check it.
Could that I/O be backed out when it's discovered that there's too many
dead disks for the array to be kept online anymore?
Just a thought,
Stephen
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-30 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 22:53 Mikulas Patocka
2005-05-29 23:01 ` Wakko Warner
2005-05-29 23:58 ` Bernd Eckenfels
2005-05-30 2:47 ` Mikulas Patocka
2005-05-30 3:00 ` Bernd Eckenfels
2005-05-30 11:55 ` Alan Cox
2005-05-30 13:23 ` Stephen Frost [this message]
2005-05-30 16:09 ` Mikulas Patocka
2005-05-31 8:05 ` Helge Hafting
2005-05-31 21:39 ` Pavel Machek
2005-06-01 1:43 ` Mikulas Patocka
2005-06-01 18:18 ` Bill Davidsen
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=20050530132328.GA30011@ns.snowman.net \
--to=sfrost@snowman.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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
all inboxes | Powered by JetHome®