From: Wols Lists <antlists@youngman.org.uk>
To: Brad Campbell <lists2009@fnarfbargle.com>,
Edward Kuns <eddie.kuns@gmail.com>
Cc: Phil Turmel <philip@turmel.org>, bobzer <bobzer@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>,
Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: raid 5 crashed
Date: Thu, 2 Jun 2016 15:01:35 +0100 [thread overview]
Message-ID: <57503C3F.6020005@youngman.org.uk> (raw)
In-Reply-To: <2f3e2fe6-1810-e7bd-7dc0-483ed4f0d46b@fnarfbargle.com>
On 02/06/16 00:15, Brad Campbell wrote:
> People keep saying that. I've never encountered it. I suspect it's just
> not the problem that the hysterical ranting makes it out to be (either
> that or the pile of cheap and nasty drives I have here are model citizens).
> I've *never* seen a read error unless the drive was in trouble, and that
> includes running dd reads in a loop over multiple days continuously.
> If it were that bad I'd see drives failing SMART long tests routinely
> also, and that does not happen either.
Note I didn't say you *will* see an error. BUT. If I recall correctly,
the specs say that one read error per 10TB read is acceptable for a
desktop drive that is designated healthy. In other words, if a 4TB drive
throws an error every third pass, then according to the spec it's a
perfectly healthy drive.
Yes. We know that most drives are far better than spec, and if it
degrades to spec then it's probably heading for failure, but the fact
remains. If you have 3 x 4TB desktop drives in an array, then the spec
says you should expect, and be able to deal with, an error EVERY time
you scan the array. (Yes, I know I would probably be panicking if I got
even one error, too :-)
Cheers,
Wol
next prev parent reply other threads:[~2016-06-02 14:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 21:28 raid 5 crashed bobzer
2016-05-11 12:09 ` Mikael Abrahamsson
2016-05-11 13:15 ` Robin Hill
2016-05-26 3:06 ` bobzer
2016-05-27 19:19 ` bobzer
2016-05-30 15:01 ` bobzer
2016-05-30 19:04 ` Anthonys Lists
2016-05-30 22:00 ` bobzer
2016-05-31 13:45 ` Phil Turmel
2016-05-31 18:49 ` Wols Lists
2016-06-01 1:48 ` Brad Campbell
2016-06-01 3:46 ` Edward Kuns
2016-06-01 4:07 ` Brad Campbell
2016-06-01 5:23 ` Edward Kuns
2016-06-01 5:28 ` Brad Campbell
2016-06-01 15:36 ` Wols Lists
2016-06-01 23:15 ` Brad Campbell
2016-06-02 5:52 ` Mikael Abrahamsson
2016-06-02 14:01 ` Wols Lists [this message]
2016-06-02 15:27 ` Andreas Klauer
2016-06-03 1:05 ` Brad Campbell
2016-06-03 7:52 ` Mikael Abrahamsson
2016-06-03 15:27 ` bobzer
2016-06-03 16:31 ` Sarah Newman
2016-06-04 2:56 ` bobzer
2016-06-01 15:42 ` Wols Lists
2016-06-01 17:28 ` Phil Turmel
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=57503C3F.6020005@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=bobzer@gmail.com \
--cc=eddie.kuns@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
--cc=philip@turmel.org \
--cc=swmike@swm.pp.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.