From: Richard Scobie <richard@sauce.co.nz>
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: Thu, 22 Apr 2010 07:24:57 +1200 [thread overview]
Message-ID: <4BCF5109.2000807@sauce.co.nz> (raw)
In-Reply-To: <4BCEFB99.9080806@tmr.com>
Bill Davidsen wrote:
> 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 can add some very limited, (6 drives) observations on the 2GB RE
version - WD2002FYPS.
These are green drives and have been running continuously in an md RAID5
for eight months without any problems and no drive settings have been
altered. This array is idle except for a nightly rsync session for an
hour or so.
Looking at the SMART data, load cycle count, is 23862 which sounds like
a lot, but the current VALUE entry is 193 (and started at 200 8 months
ago) and the THRESHOLD value is 0.
So, if I am interpreting this trend correctly, the THRESHOLD value will
be reached in about 682,000 load cycles and about 228 months.
Regards,
Richard
next prev parent reply other threads:[~2010-04-21 19:24 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
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 [this message]
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=4BCF5109.2000807@sauce.co.nz \
--to=richard@sauce.co.nz \
--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).