From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Redeeman <redeeman@metanurb.dk>
Cc: Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
xfs@oss.sgi.com, smartmontools-support@lists.sourceforge.net
Subject: Re: Have the velociraptors in a test system now, checkout the errors.
Date: Sun, 14 Dec 2008 04:05:11 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.0812140404090.28949@p34.internal.lan> (raw)
In-Reply-To: <1229225303.16555.149.camel@localhost>
On Sun, 14 Dec 2008, Redeeman wrote:
> On Wed, 2008-12-10 at 19:11 -0500, Bill Davidsen wrote:
>> Justin Piszcz wrote:
>>> Point of thread: Two problems, mentioned in detail below, NCQ in Linux
>>> when used in a RAID configuration and two, something with how Linux
>>> interacts with the drives causes lots of problems as when I run the WD
>>> tools on the disks, they do not show any errors.
>>>
>>> If anyone has/would like me to run any debugging/patches/etc on this
>>> system feel free to suggest/send me things to try out. After I put
>>> the VR's in a test system, I left NCQ enabled and I made a 10 disk
>>> raid5 to see how fast I could get it to fail, I ran bonnie++ shown
>>> below as a disk benchmark/stress test:
>>>
>>> For the next test I will repeat this one but with NCQ disabled, having
>>> NCQ enabled makes it fail very easily. Then I want to re-run the test
>>> with RAID6.
>>>
>>> bonnie++ -d /r1/test -s 1000G -m p63 -n 16:100000:16:64
>>>
>>> $ df -h
>>> /dev/md3 2.5T 5.5M 2.5T 1% /r1
>>>
>>> And the results? Two disk "failures" according to md/Linux within a
>>> few hours as shown below:
>>>
>>> Note, the NCQ-related errors are what I talk about all of the time, if
>>> you use
>>> NCQ and Linux in a RAID environment with WD drives, well-- good luck.
>>>
>>> Two-disks failed out of the RAID5 and I currentlty cannot even 'see'
>>> one of the drives with smartctl, will reboot the host and check sde
>>> again.
>>>
>>> After a reboot, it comes up and has no errors, really makes one wonder
>>> where/what the bugs is/are, there are two I can see:
>>> 1. NCQ issue on at least WD drives in Linux in SW md/RAID
>>> 2. Velociraptor/other disks reporting all kinds of sector errors etc,
>>> but when you use the WD 11.x disk tools program and run all of their
>>> tests it says the disks have no problems whatsoever! The smart
>>> statistics do confirm this. Currently, TLER is on for all disks, for
>>> the duration of these tests.
>>
>> Just a few comments on this, I have several RAID arrays built on Seagate
>> using NCQ, and yet to have a problem. I have NCQ on with my WD drives,
>> non-RAID, and haven't had an issue with them either. The WDs run a lot
>> cooler than the SG, but they are probably getting less use, as well. If
>> the WD are still on sale after the holiday I may grab a few more and run
>> RAID, by then I will have some small sense of trusting them.
> Velociraptors, or which WD?
Velociraptors or Raptors or 750GiB disks (in Linux SW Raid) the NCQ issue
does not appear to occur on Raptors on a 3ware card though, only in
Linux+SW_raid. The regular raptor/750gib also run just fine as standalone
with NCQ.
Justin.
next prev parent reply other threads:[~2008-12-14 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 9:51 Justin Piszcz
2008-12-06 11:13 ` Michael Tokarev
2008-12-06 12:11 ` Justin Piszcz
2008-12-06 20:55 ` Kyle Moffett
2008-12-06 23:22 ` Michael Tokarev
2008-12-11 0:11 ` Bill Davidsen
2008-12-14 3:28 ` Redeeman
2008-12-14 9:05 ` Justin Piszcz [this message]
[not found] ` <4949645F.4030407@tmr.com>
2008-12-17 23:21 ` Justin Piszcz
2008-12-18 23:14 ` Bill Davidsen
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=alpine.DEB.1.10.0812140404090.28949@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=redeeman@metanurb.dk \
--cc=smartmontools-support@lists.sourceforge.net \
--cc=xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®