9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: W B Hacker <wbh@conducive.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Recovering a venti from disk failure
Date: Fri, 20 Apr 2007 05:39:35 +0800	[thread overview]
Message-ID: <4627E197.90804@conducive.org> (raw)
In-Reply-To: <b0b46a1f773b9a5a73bb3bb5aedb7b74@coraid.com>

erik quanstrom wrote:
>> Various studies seem to indicate failure rates are highly
>> correlated with drive model, vintage and manufacturer.
>> Assuming a RAID is built from similar disks, when one fails
>> the others are more likely to fail.
> 
> while it is true that some disks vintages are better than others, when
> one drive fails, the probability of the other drives failing has not
> changed.  this is the same as if you flip a coin ten times and get ten
> heads, the probability of flipping the same coin and getting heads, is
> still 1/2.
> 
>>> i think this corelation gives people the false impression that they do
>>> fail en masse, but that's really wrong.  the latent errors probablly
>>> happened months ago.
>> Yes but if there are many latent errors and/or the error rate
>> is going up it is time to replace it.
> 
> maybe.  the goggle paper you cited didn't find a strong correlation
> between smart errors (including block relocation) and failure.
> 
>> This is a good idea.  We did this in 1983, back when disks
>> were simpler beasts.  No RAID then of course.
> 
> even a better idea back then.  disks didn't have 1/4 million
> lines of firmware relocating blocks and doing other things to^w
> i mean for you.
> 
> - erik
> 
> 

And - lest we forget - a RAID array actually has a higher statistical chance of 
failure, and a *lower* MTBF than a single drive. Simple math.

What we gain is a reduced risk of *unrecoverable* damage, not fewer failures, 
per se.

Bill





  reply	other threads:[~2007-04-19 21:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19  4:05 Anthony Sorace
2007-04-19  4:30 ` Russ Cox
2007-04-19  4:48 ` Bakul Shah
2007-04-19  5:43 ` geoff
2007-04-19  6:07   ` Bakul Shah
2007-04-19 12:05     ` erik quanstrom
2007-04-19 20:15       ` Bakul Shah
2007-04-19 21:26         ` erik quanstrom
2007-04-19 21:39           ` W B Hacker [this message]
2007-04-19 22:25           ` Bakul Shah
2007-04-19 21:36         ` W B Hacker
2007-04-19 11:25   ` Anthony Sorace
2007-04-19 12:01     ` Russ Cox
2007-04-19  4:37 YAMANASHI Takeshi

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=4627E197.90804@conducive.org \
    --to=wbh@conducive.org \
    --cc=9fans@cse.psu.edu \
    /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).