linux-kernel - Re: Velociraptor drive related to the use of NCQ.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 6 Dec 2008 04:26:18 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
	xfs@....sgi.com, smartmontools-support@...ts.sourceforge.net
cc:	Alan Piszcz <ap@...arrain.com>
Subject: Re: Velociraptor drive related to the use of NCQ.



On Fri, 5 Dec 2008, Justin Piszcz wrote:

>
>
> On Fri, 5 Dec 2008, Justin Piszcz wrote:
>
>> I swapped out my power supply, changed ALL cables and bought a $1000 raid
>> controller with BBU, the drives are still having problems, when writing to
>> them in a RAID10 configuration, it locks up the card:
>> 
>> SMART shows the same thing on many of the disks in the RAID10:
>> 
>> Error 1 occurred at disk power-on lifetime: 3708 hours (154 days + 12 
>> hours)
>>  When the command that caused the error occurred, the device was active or 
>> idle.
>
> I spoke to soon, turning off NCQ helped dramatically, it worked three times!
>
> writing to raid10
> dd: writing `file2': No space left on device
> 1430328+0 records in
> 1430327+0 records out
> 1499806973952 bytes (1.5 TB) copied, 3914.51 s, 383 MB/s
> Fri Dec  5 06:00:25 EST 2008
> writing to raid10
> dd: writing `file2': No space left on device
> 1430328+0 records in
> 1430327+0 records out
> 1499806973952 bytes (1.5 TB) copied, 4063.25 s, 369 MB/s
> Fri Dec  5 07:08:11 EST 2008
> writing to raid10
> dd: writing `file2': No space left on device
> 1430328+0 records in
> 1430327+0 records out
> 1499806973952 bytes (1.5 TB) copied, 3926.71 s, 382 MB/s
> Fri Dec  5 08:13:41 EST 2008
>
> Then it crashed again, with NCQ enabled, it would not even complete one test,
> So basically a new system, new PSU, new cables, its on a new APC UPS and the 
> problem persists even when all disks are on a RAID card, SW raid, it does not 
> matter, Velociraptors have problems, I think its time for me to get regular
> 1TiB disks and be done with it.
>
> Justin.
>
>

I have swapped my disks:

Removed my 12 velociraptors.
Inserted my old 12 raptor150s (all ADFD).

The 12 velociraptors are now in a test system using md/raid.
The 12 raptor 150s are now in my main machine w/3ware.

I am going to run the same tests, benchmarks, etc and see if any problems 
repeat with the 150s and I will also run a bunch more tests on the 
velociraptors as well.

So far no problems with the good ol' raptor 150s and I have been running 
the same dd test for the past 8 hours+ on the same raid type and settings 
as I had with the velociraptors:

Fri Dec  5 21:07:43 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2747.77 s, 273 MB/s
Fri Dec  5 21:53:32 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2742.29 s, 273 MB/s
Fri Dec  5 22:39:17 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2685.21 s, 279 MB/s
Fri Dec  5 23:24:05 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2600.05 s, 288 MB/s
Sat Dec  6 00:07:28 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2550.45 s, 294 MB/s
Sat Dec  6 00:50:02 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2507.31 s, 299 MB/s
Sat Dec  6 01:31:52 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2247.31 s, 334 MB/s
Sat Dec  6 02:09:22 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2248.2 s, 334 MB/s
Sat Dec  6 02:46:53 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2245.41 s, 334 MB/s
Sat Dec  6 03:24:22 EST 2008
dd: writing `/t/bigfile': No space left on device
715067+0 records in
715066+0 records out
749801271296 bytes (750 GB) copied, 2494.1 s, 301 MB/s
Sat Dec  6 04:05:59 EST 2008

So far no problems, just like before when I used to use these drives in 
the past, they are rock solid (will continue to test, the VRs are another 
story)-- more info soon to follow.

Justin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/