From: Peter Kieser <peter@kieser.ca>
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:51:09 -0700 [thread overview]
Message-ID: <508DC4ED.3030706@kieser.ca> (raw)
In-Reply-To: <11510711257.20121028131527@oudeis.org>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
I've had interesting cases where WD Green Drives (specifically WD15EARS,
WD15EADS) don't necessarily "fail" but suddenly have very slow
random/read write performance which slows down the rest of the array.
Removing the drive, and replacing it with a (new) drive usually resolves
the issue. I have since started to avoid "green" drives due to this issue.
-Peter
On 2012-10-28 5:15 AM, 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)
>
> tnx.
>
> --
> 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
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4504 bytes --]
prev parent reply other threads:[~2012-10-28 23:51 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
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 [this message]
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=508DC4ED.3030706@kieser.ca \
--to=peter@kieser.ca \
--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).