From: Andi Kleen <ak@muc.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: critical bugs in md raid5 and ATA disk failure/recovery modes
Date: 29 Jan 2005 19:37:31 +0100
Date: Sat, 29 Jan 2005 19:37:31 +0100 [thread overview]
Message-ID: <20050129183731.GA40659@muc.de> (raw)
In-Reply-To: <20050129183511.GA2055@elf.ucw.cz>
> Well, you could set stripe size to 512B; that way, RAID-5 would be
> *very* slow, but it should have same characteristics as normal disc
> w.r.t. crash. Unrelated data would not be lost, and you'd either get
> old data or new data...
When you lose a disk during recovery you can still lose
unrelated data (any "sibling" in a stripe set because its parity
information is incomplete). RAID-1 doesn't have this problem though.
-Andi
next prev parent reply other threads:[~2005-01-29 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 3:59 critical bugs in md raid5 Marc Lehmann
2005-01-27 5:11 ` Andi Kleen
2005-01-27 6:31 ` Marc Lehmann
2005-01-27 9:51 ` Andi Kleen
2005-01-27 16:33 ` critical bugs in md raid5 and ATA disk failure/recovery modes Marc Lehmann
2005-01-29 18:35 ` Pavel Machek
2005-01-29 18:37 ` Andi Kleen [this message]
2005-01-29 18:55 ` Pavel Machek
2005-01-27 16:56 ` critical bugs in md raid5 Lehmann
2005-01-27 6:48 ` Lehmann
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=20050129183731.GA40659@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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