From: John Robinson <john.robinson@anonymous.org.uk>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Dawning Sky <the.dawning.sky@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Disk I/O error while rebuilding an md raid-5 array
Date: Tue, 09 Feb 2010 11:57:06 +0000 [thread overview]
Message-ID: <4B714D92.2090802@anonymous.org.uk> (raw)
In-Reply-To: <87f94c371002081604g37984161h2ba65bd193714780@mail.gmail.com>
On 09/02/2010 00:04, Greg Freemyer wrote:
>> PS, if in the end I have to build a new array, I'll probably go with a
>> raid 6 instead.
>
> Agreed, someone recently posted that for a raid-5 composed of 1TB
> drives the odds of a rebuild failure are 1 in 67 even if the remaining
> drives are within spec. (ie. the unrecoverable bit error rate is
> slowing succumbing to the ever increasing size of drives.)
Actually the odds were 1 in 67 of an unrecoverable read error while
reading 2TB of data, if the odds were 1 in 10^15 per bit read[1], which
was the worst-case spec offered by Western Digital. Others disagreed
with my analysis, and I may be wrong.
This was nothing to do with RAID, but my suggestion followed on that
RAID-5 was now only useful for defending against unrecoverable errors,
and not dead drives, and if you wanted to defend against dead drives as
well you need RAID-6.
> You have 500GB drives, but you have 3 left to rebuild from, so that's
> 1.5 TB your trying to read. I'm not sure how the original calculation
> was done, so your odds of failed rebuild were either 1 in 134 or about
> 1 in 42. Either not very good for something that is supposed to
> protect your data.
Actually there are 4 to read from - the original sde is still available.
This would be a situation where I think having the hot-rebuild facility
recently discussed on this list would be ideal, as if you can't read the
data from the drive you're hot-replacing, you then get a second chance
to read it from the rest of the drives using the parity information, and
the odds of an unrecoverable read error at the same LBA on two drives is
smaller - but I can't remember that bit of the probability course I did
years ago to work out exactly what it is.
Cheers,
John.
[1] If the probability of an error while reading 1 bit is p, then the
probability of an error while reading n bits is 1-(1-p)^n. In this case
p=1E-15, n=1.6E13 and you need a scientific calculator to do the sum.
next prev parent reply other threads:[~2010-02-09 11:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 23:23 Disk I/O error while rebuilding an md raid-5 array Dawning Sky
2010-02-09 0:04 ` Greg Freemyer
2010-02-09 0:45 ` Dawning Sky
2010-02-09 10:22 ` Jon Hardcastle
2010-02-09 11:57 ` John Robinson [this message]
2010-02-09 17:43 ` Dawning Sky
2010-02-09 19:28 ` Mikael Abrahamsson
2010-02-09 1:23 ` Dawning Sky
2010-02-09 4:24 ` Wil Reichert
2010-02-09 4:26 ` Steven Haigh
2010-02-09 4:37 ` Wil Reichert
2010-02-09 4:20 ` Dawning Sky
2010-02-09 6:57 ` Stefan Hübner
2010-02-09 7:39 ` Dawning Sky
2010-02-09 8:05 ` Mikael Abrahamsson
-- strict thread matches above, loose matches on Subject: below --
2010-02-09 0:25 russ
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=4B714D92.2090802@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=greg.freemyer@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=the.dawning.sky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).