From: Bill Davidsen <davidsen@tmr.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: st0ff@npl.de, linux-raid@vger.kernel.org
Subject: Re: Use of WD20EARS with MDADM
Date: Wed, 21 Apr 2010 12:42:04 -0400 [thread overview]
Message-ID: <4BCF2ADC.1020600@tmr.com> (raw)
In-Reply-To: <4BCF163C.6040604@cfl.rr.com>
Phillip Susi wrote:
> On 4/21/2010 9:20 AM, Bill Davidsen wrote:
>
>> I hear this said, but I don't have any data to back it up. Drive vendors
>> aren't stupid, so if the parking feature is likely to cause premature
>> failures under warranty, I would expect that the feature would not be
>> there, or that the drive would be made more robust. Maybe I have too
>> much faith in greed as a design goal, but I have to wonder if load
>> cycles are as destructive as seems to be the assumption.
>>
>
> Indeed, I think you have too much faith in people doing sensible things.
> Especially when their average customer isn't placing the drive in a
> high use environment and they know it, and suggest against doing so.
>
>
>> I'd love to find some real data, anecdotal stories about older drives
>> are not overly helpful. Clearly there is a trade-off between energy
>> saving, response, and durability, I just don't have any data from a
>> large population of new (green) drives.
>>
>
> I've not seen any anecdotal stories, but I have seen plenty of reports
> with real data showing a large number of head unloads from the SMART
> data after a relatively short period of use. Personally mine has a few
> hundred so far and I have not even used it for real storage yet, only
> testing. The specifications say it's good for 300,000 cycles, so do the
> math... getting 5 unloads per minute would lead to probable failure
> after 41 days. Granted that is about worst case, but still something to
> watch out for. In order to make it the entire 3 year warranty period,
> you need to stay under 11.4 unloads per hour. If you have very little
> IO activity, or VERY MUCH, then this is entirely possible, but more
> moderate loads in the middle have been observed to cause hundreds of
> unloads per hour.
>
> Given that, and the fact that WD themselves have stated that you should
> not use these drives in a raid array, I'd either stay away, or watch out
> for this problem and try to take action to avoid and monitor it.
>
Part of this is my feeling that no one really knows if the drive fails
after N loads, because even if WD could set the unload time down, the
cycle takes time to happen, so I would bet that they are taking an
educated guess. The other part is that there are lots of clerical tasks
which would hit the drive, under Windows, single drive, 3-5 times a
minute. Data entry comes to mind, customer support, print servers, etc.
Granted that these are probably 7x5 hours a week, but I'm think 2/min,
7hr/day, 200day/yr... 168k/yr, and that's not the worst case.
Having run lots of drives (some TB of 73GB 15k rpm LVD320) MTTF is
interesting, because the curve has spikes at the front from infant
mortality, and at the end from old age, but it was damn quiet in the
middle. I'd love to see the data on these, not because I'm going to run
them but just to keep current, so when someone calls me and says they
got a great deal on green drives, I'll know what to tell them.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
next prev parent reply other threads:[~2010-04-21 16:42 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 16:20 Use of WD20EARS with MDADM Andrew Dunn
2010-03-25 17:01 ` Asdo
2010-03-25 17:58 ` Mark Knecht
2010-03-25 20:23 ` John Robinson
2010-03-26 10:45 ` Asdo
2010-03-25 17:10 ` David Lethe
2010-03-25 17:45 ` Asdo
2010-03-28 16:19 ` Stefan *St0fF* Huebner
2010-03-29 16:59 ` WD20EARS data Stefan /*St0fF*/ Hübner
2010-03-29 17:13 ` Stefan /*St0fF*/ Hübner
2010-04-14 19:53 ` Use of WD20EARS with MDADM Bill Davidsen
2010-04-19 14:17 ` Phillip Susi
2010-04-21 13:20 ` Bill Davidsen
2010-04-21 13:45 ` Tim Small
2010-04-21 14:32 ` Mikael Abrahamsson
2010-04-21 21:58 ` Berkey B Walker
2010-05-02 22:33 ` Bill Davidsen
2010-05-03 0:08 ` Berkey B Walker
2010-04-21 15:14 ` Phillip Susi
2010-04-21 16:42 ` Bill Davidsen [this message]
2010-04-21 17:36 ` Mark Knecht
2010-04-21 18:40 ` Tim Small
2010-04-21 19:01 ` Mark Knecht
2010-04-21 19:31 ` Clinton Lee Taylor
2010-04-22 0:51 ` Steven Haigh
2010-04-21 19:33 ` Phillip Susi
2010-04-21 20:36 ` Mark Knecht
2010-05-12 13:06 ` Tim Small
2010-04-22 11:40 ` wdidle3 Tim Small
2010-04-22 16:13 ` Use of WD20EARS with MDADM Khelben Blackstaff
2010-04-22 18:16 ` Simon Matthews
2010-04-22 19:44 ` Phillip Susi
2010-04-22 23:23 ` Mark Knecht
2010-04-23 0:03 ` Richard Scobie
2010-04-23 1:29 ` Mark Knecht
2010-04-23 3:49 ` Phillip Susi
2010-04-23 3:44 ` Phillip Susi
2010-04-21 15:52 ` Simon Matthews
2010-04-21 19:24 ` Richard Scobie
2010-03-26 20:27 ` Peter Kieser
2010-03-26 20:59 ` Mark Knecht
2010-03-26 21:01 ` Peter Kieser
2010-03-26 21:06 ` Mark Knecht
2010-03-26 21:16 ` Mark Knecht
2010-03-26 21:19 ` Richard Scobie
2010-03-26 22:38 ` Mark Knecht
2010-03-26 22:47 ` Peter Kieser
2010-03-26 22:50 ` Matt Garman
2010-03-26 22:51 ` Peter Kieser
2010-03-26 23:01 ` David Rees
2010-03-27 23:31 ` Mark Knecht
2010-03-26 21:45 ` Matt Garman
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=4BCF2ADC.1020600@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--cc=st0ff@npl.de \
/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).