From: joystick <joystick@shiftmail.org>
To: Joe Landman <joe.landman@gmail.com>
Cc: "Ed W" <lists@wildgooses.com>,
"Rainer Fügenstein" <rfu@oudeis.org>,
linux-raid@vger.kernel.org
Subject: Re: 3TB drives failure rate
Date: Sun, 28 Oct 2012 23:12:19 +0100 [thread overview]
Message-ID: <508DADC3.4080104@shiftmail.org> (raw)
In-Reply-To: <508D65CF.1080904@gmail.com>
On 10/28/12 18:05, Joe Landman wrote:
> On 10/28/2012 12:47 PM, Ed W wrote:
>
>> - 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...
>
> Our experience is that they aren't acceptable for RAIDs in most cases,
> unless you turn on TLER, and turn off the green functions at minimum.
> In which case, what advantage do they have other than price?
Do you have a magic way to turn on TLER on green drives and would like
to share it with us?
I can give you money
smartctl scterc did not work there, last time I checked
> Part of the issue is them falling out of RAIDs. Part of the the issue
> are the occasional hiccups on coming out of sleep mode, which for most
> desktops isn't a problem, but DEFINITELY an issue for RAIDs.
This thing of "drives falling out of RAID" I have heard many times, but
really don't know what people are talking about.
How could a drive fall out of a RAID? A RAID is nothing special, it's
just read/write commands given to a drive by a process called MD.
If the drive drops out of RAID it means it would have dropped out of a
normal computer doing normal I/O
Please explain
>
> Another (sometimes significant) issue is that we've been noticing
> partial coverage (e.g. missing functions) in some of the pages
> available to sdparm with the desktop/consumer drives. This is very
> annoying, especially if you are building a RAID. Most egregious on
> SSDs, but we've seen one spinning rust device that did the same.
These sdparm missing feature also would interest me,
but actually less than a response to the other 2 topics above
next prev parent reply other threads:[~2012-10-28 22:12 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 [this message]
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=508DADC3.4080104@shiftmail.org \
--to=joystick@shiftmail.org \
--cc=joe.landman@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@wildgooses.com \
--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 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.