From: Phillip Susi <psusi@cfl.rr.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: st0ff@npl.de, linux-raid@vger.kernel.org
Subject: Re: Use of WD20EARS with MDADM
Date: Mon, 19 Apr 2010 10:17:15 -0400 [thread overview]
Message-ID: <4BCC65EB.3080803@cfl.rr.com> (raw)
In-Reply-To: <4BC61D47.6090403@tmr.com>
On 4/14/2010 3:53 PM, Bill Davidsen wrote:
> Stefan *St0fF* Huebner wrote:
>> Am 25.03.2010 18:45, schrieb Asdo:
>>
>>> David Lethe wrote:
>>>
>>>> On Mar 25, 2010, at 11:20 AM, Andrew Dunn wrote:
>>>>
>>>>
>>>>> Recently Dell is selling their WD20EARS (2TB) for 90$
>>>>>
>>>>> This being one of the best PPG (Price Per Gigabyte) snatches I have
>>>>> seen, I was considering buying 8 of them for an mdadm array.
>>>>>
>>>>> Has anyone had experience with these drives?
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".
next prev parent reply other threads:[~2010-04-19 14:17 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 [this message]
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
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=4BCC65EB.3080803@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--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).