From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: raid failure question
Date: Mon, 11 Jan 2010 20:53:32 +0000 [thread overview]
Message-ID: <20100111205332.GA24486@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <1263232840.8962.193.camel@kije>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Mon Jan 11, 2010 at 11:00:40AM -0700, Tim Bock wrote:
> Hello,
>
> Excluding the obvious multi-disk or bus failures, can anyone describe
> what type of disk failure a raid cannot detect/recover from?
>
> I have had two disk failures over the last three months, and in spite of
> having a hot spare, manual intervention was required each time to make
> the raid usable again. I'm just not sure if I'm not setting something
> up right, or if there is some other issue.
>
> Thanks for any comments or suggestions.
>
Any failure where the disk doesn't actually return an error (within a
reasonable time). For example, consumer grade disks often have very
long retry times - this can mean the array in unusable for a long time
until the disk eventually fails the read.
If the disk actually returns an error then, AFAIK, the RAID array should
always be able to recover from it.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-11 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 18:00 raid failure question Tim Bock
2010-01-11 18:08 ` Majed B.
2010-01-11 20:44 ` Thomas Fjellstrom
2010-01-11 20:53 ` Robin Hill [this message]
2010-01-12 12:08 ` Roger Heflin
2010-01-12 15:07 ` Tim Bock
2010-02-01 20:19 ` Bill Davidsen
2010-01-12 4:47 ` Leslie Rhorer
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 20:29 David Lethe
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=20100111205332.GA24486@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
/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).