From: "Majed B." <majedb@gmail.com>
To: Tim Bock <jtbock@daylight.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid failure question
Date: Mon, 11 Jan 2010 21:08:57 +0300 [thread overview]
Message-ID: <70ed7c3e1001111008y76b49b8bve2b636c90efa4a72@mail.gmail.com> (raw)
In-Reply-To: <1263232840.8962.193.camel@kije>
Voltage spikes, disks heating (monitored by smartd) & sector
corruption (monitored by smartd) are what I can think of for the time
being.
On Mon, Jan 11, 2010 at 9:00 PM, Tim Bock <jtbock@daylight.com> 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.
>
> Tim
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Majed B.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-11 18:08 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. [this message]
2010-01-11 20:44 ` Thomas Fjellstrom
2010-01-11 20:53 ` Robin Hill
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=70ed7c3e1001111008y76b49b8bve2b636c90efa4a72@mail.gmail.com \
--to=majedb@gmail.com \
--cc=jtbock@daylight.com \
--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).