From: Brad Campbell <lists2009@fnarfbargle.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: HDD reports errors while completing RAID6 array check
Date: Tue, 14 Jun 2011 08:15:32 +0800 [thread overview]
Message-ID: <4DF6A824.6070502@fnarfbargle.com> (raw)
In-Reply-To: <4DF65758.2030405@gmail.com>
On 14/06/11 02:30, Tim Blundell wrote:
>
> On 6/11/2011 5:49 AM, Mathias Burén wrote:
>> === START OF INFORMATION SECTION ===
>> Model Family: Western Digital Caviar Green (Adv. Format) family
>> Device Model: WDC WD20EARS-00MVWB0
>> Serial Number: WD-WMAZ20188479
>> Firmware Version: 50.0AB50
>> User Capacity: 2,000,398,934,016 bytes
>> Device is: In smartctl database [for details use: -P show]
>> ATA Version is: 8
>> ATA Standard is: Exact ATA specification draft version not indicated
>> Local Time is: Sat Jun 11 10:48:05 2011 IST
>> SMART support is: Available - device has SMART capability.
>> SMART support is: Enabled
>
> Not certain if this was mentioned. While WDC WD20EARS drives can be used in an RAID array, WD
> recommends using there RAID capable drives in an enterprise environment.
> I tried using same drives in a simple RAID-1 array and had serious performance issues (sync taking
> a week) and stalls when writing to disk. Are you using the stock firmware on these drives?
Just a data point. I have 10 of them in a RAID-6. They are in a 6 core / 16GB box with PCIe SAS
controllers (so the machine is not bandwidth starved). I hammer the living daylights out of them.
They are quite fast for sequential access, not very fast for random IO and they are pretty cool and
quiet.
I have used WDIDLE3 to turn off the idle timer to stop the heads unloading though.
The reason WD state their consumer drives are no good in RAID applications is TLER. On a hardware
RAID controller the drives can get kicked out of the array if they go into a deep recovery read, but
md does not suffer this issue.
On SMART, it's prudent to configure smartmontools to do regular checks and e-mail you if it sees an
issue. I do a long every sunday and shorts every other morning and have had early notification of
pending issues a couple of times. Definitely worth the price of admission.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-06-14 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 17:37 HDD reports errors while completing RAID6 array check Mathias Burén
2011-06-10 18:00 ` Roman Mamedov
2011-06-10 18:23 ` Mathias Burén
2011-06-11 9:49 ` Mathias Burén
2011-06-13 18:30 ` Tim Blundell
2011-06-13 18:41 ` Mathias Burén
2011-06-15 9:11 ` Gordon Henderson
2011-06-14 0:15 ` Brad Campbell [this message]
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=4DF6A824.6070502@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=linux-raid@vger.kernel.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 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).