linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Small <tim@seoss.co.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Phillip Susi <psusi@cfl.rr.com>,
	st0ff@npl.de, linux-raid@vger.kernel.org
Subject: Re: Use of WD20EARS with MDADM
Date: Wed, 21 Apr 2010 14:45:38 +0100	[thread overview]
Message-ID: <4BCF0182.40400@seoss.co.uk> (raw)
In-Reply-To: <4BCEFB99.9080806@tmr.com>

Bill Davidsen wrote:
>> I believe that these disks only come in the "green" variety.  I recently
>> picked up a 1.5 tb version for testing and cheap bulk storage, and I
>> would not suggest using them in a raid array because the green drives
>> firmware automatically parks the head after 8 seconds of inactivity and
>> reduces the rpm of the disk.  The constant parking can quickly wear out
>> the head under high use and there is no way to disable this "feature".
>>   
>
> 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.

I've used the 500G, and 2TB WD consumer green drives in md arrays, not
many - about 10 in total.  The older 500G drives (like many WD 2.5"
drives) did frequent head unload/reloads under Linux due to interactions
with the default timings of the Linux block layer, I believe.  This can
be fixed using WD's wdidle3.exe under DOS.  You can monitor this using
smartctl - look at the raw value for unloads, but it shouldn't be an
issue with newer drives.

Both the 2TB and 500G drives seem to lock up and need resetting by Linux
(this happens automatically) if you poll the SMART status e.g. you run
smartd, or munin+smartctl etc. (the 2TB drives that I've had also seem
to occasionally lock up under other workloads, but you might be able to
live with this) - the SMART thing might be a firmware bug but WDC say
"contact your Linux vendor" - they only provide support for Windows - I
must get around to polling one of them for SMART under Windows XP for
comparison.

If you're going to be trying to use a load of them in a RAID, then you
need to be careful about vibration damping - they may not cope that well
with vibration (check SMART high-fly-writes and hardware-ecc-recovered
raw values if available).  They are also not rated for 24/7 operation, I
believe.

Tim.

-- 
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.  
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53  http://seoss.co.uk/ +44-(0)1273-808309


  reply	other threads:[~2010-04-21 13:45 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 [this message]
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
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=4BCF0182.40400@seoss.co.uk \
    --to=tim@seoss.co.uk \
    --cc=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).