From: Ed W <lists@wildgooses.com>
To: "Rainer Fügenstein" <rfu@oudeis.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: 3TB drives failure rate
Date: Sun, 28 Oct 2012 16:47:29 +0000 [thread overview]
Message-ID: <508D61A1.7020106@wildgooses.com> (raw)
In-Reply-To: <11510711257.20121028131527@oudeis.org>
On 28/10/2012 12:15, Rainer Fügenstein wrote:
> when trying to upgrade my raid5 with 4 Western digital caviar green
> 3TB drives [WDC WD30EZRX-00MMMB0] (3 brandnew, 1 about 4months old),
> the "old" drive and one of the brand new ones failed with
> unrecoverable read errors and about 70 reallocated sectors each. the
> failures already occured during the initial resync after creating the
> raid.
>
> until now I was very fond of WD caviar green drives, but after this
> 50% failure rate I'm not very eager to restore data from the backup.
>
> what is your experience with 3TB drives, WD and others?
>
> (low power drives appreciated, performance is not an issue)
>
I think there is clearly serial correlation in drive failures and this
tends to cause people to have brand love/hate stories.
I bought 9x Samsung 2TB green things about 2 years back (to go in an 8x
NAS + 1 spare). I think I had to return 4 almost immediately due to
either out of box reallocation warning, or that appeared within 2
weeks. Probably if I hadn't been looking I wouldn't have noticed these
warnings and then been one of those groaning about Samsung when probably
they all expired within a few weeks of each other. The RMA'd drives
have all been fine and the whole array seems ok some years later (tested
weekly). Note that I think I got 2x drives from a different supplier
(hence different batch), so that implies something like 4 out of 7 in a
given batch were "worrying", but the next 4 from a new batch showed no
obvious problems
I think this fits with the idea that the spinning disk failure curve has
a bump in the first few weeks, then flat until some years later when it
peaks again...
My conclusion:
- RAID6 for data that is highly valuable (and performance is acceptable)
- Thrash the drives initially for some weeks before you accept them into
production.
- Although highly debated, I believe that failures are likely to be
correlated in time, when one drive goes there is a high probability of
loosing others in the next 24 hours. Take precautions as you see fit, eg
regular backups, hot/warm spares, etc
- Green consumer drives likely are satisfactorarily reliable for most
uses, caveat that you accept they will fail catastrophically eventually
(just like your enterprise drive will). We can debate the relative life
of each, but it's almost certainly just a linear factor...
Good luck
Ed W
--
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:[~2012-10-28 16:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 12:15 3TB drives failure rate Rainer Fügenstein
2012-10-28 12:19 ` Mathias Burén
2012-10-28 12:49 ` John Robinson
2012-10-28 12:54 ` Michael Tokarev
2012-10-28 16:47 ` Ed W [this message]
2012-10-28 17:05 ` Joe Landman
2012-10-28 22:12 ` joystick
2012-10-28 22:24 ` Miles Fidelman
2012-10-28 23:59 ` joystick
2012-10-29 0:09 ` Miles Fidelman
2012-10-29 4:29 ` Roman Mamedov
2012-10-29 7:54 ` David Brown
2012-10-29 13:02 ` Phil Turmel
2012-10-30 23:54 ` 3TB drives failure rate (summary) Rainer Fügenstein
2012-10-31 12:35 ` Phil Turmel
2012-11-01 15:13 ` Miles Fidelman
2012-11-01 15:24 ` John Robinson
2012-11-01 15:39 ` Miles Fidelman
2012-11-01 16:05 ` John Robinson
2012-11-01 16:25 ` Miles Fidelman
2013-02-05 17:43 ` Adam Goryachev
2013-02-05 18:08 ` Roy Sigurd Karlsbakk
2013-02-05 20:34 ` Wolfgang Denk
2012-10-29 13:26 ` 3TB drives failure rate Miles Fidelman
2012-10-28 19:50 ` Chris Murphy
2012-10-28 19:59 ` Roman Mamedov
2012-10-28 20:10 ` Chris Murphy
2012-10-28 20:16 ` Roman Mamedov
2012-10-28 20:34 ` Chris Murphy
2012-10-28 20:49 ` Roman Mamedov
2012-10-28 20:59 ` Chris Murphy
2012-10-28 21:07 ` Miles Fidelman
2012-10-28 20:50 ` Chris Murphy
2012-10-28 21:07 ` Chris Murphy
2012-10-28 21:18 ` Roman Mamedov
2012-10-28 21:24 ` Mikael Abrahamsson
2012-10-28 21:45 ` Miles Fidelman
2012-10-28 22:35 ` Chris Murphy
2012-10-28 21:51 ` Chris Murphy
2012-10-28 21:59 ` joystick
2012-10-28 22:10 ` Phil Turmel
2012-10-29 0:12 ` joystick
2012-10-29 0:21 ` Phil Turmel
2012-10-29 0:27 ` Chris Murphy
2012-10-28 21:21 ` Mikael Abrahamsson
2012-10-28 23:51 ` Peter Kieser
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=508D61A1.7020106@wildgooses.com \
--to=lists@wildgooses.com \
--cc=linux-raid@vger.kernel.org \
--cc=rfu@oudeis.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).