linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: linux@horizon.com
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_sil24 test support
Date: Tue, 22 Nov 2005 10:52:02 +0900	[thread overview]
Message-ID: <438279C2.6030002@gmail.com> (raw)
In-Reply-To: <20051122002333.9619.qmail@science.horizon.com>

linux@horizon.com wrote:
>>One thing I wanna verify on sil24 is data integrity with multiple disks 
>>attached.  It would be very helpful if you can do some parallel data 
>>stress testing with multiple disks.
>>
>>* Parallel 'badblocks -w -t random' on all attached disks.  Maybe repeat 
>>it for a few days and verify no corrupted IO occurs.
> 
> 
> Just completed 6 passes x 6 drives x 350 GB = 12.6 TB of badblocks (10^14
> bits) with no errors.  That's in addition to a previous 5 passes that
> was interrupted by timeout problems on one drive, but that's an error
> handling issue and not a data corruption problem, and it did resolve
> itself eventually after I killed the badblocks run.
> 
> That's several days of solid disk access at > 300 MB/sec.
> (Some silly people asked me why I ingored the Sil3114 that came with
> the motherboard...)
> 
> Thanks for a great driver!  I'll have even more fun testing NCQ one of
> these days. :-)
> 
> Now rebooting to 2.6.14-rc2.  Now that it's stable, this system is going
> into production Very Very Soon.  If you want any more testing, speak up!

I'm very glad to here the good news.  I'll let you know when more
testing is needed.  Thanks for doing this.

-- 
tejun

  reply	other threads:[~2005-11-22  1:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  9:59 sata_sil24 corruption details linux
2005-11-07 16:15 ` Greg Freemyer
2005-11-10  7:17 ` linux
2005-11-10  9:01   ` Tejun Heo
2005-11-10 14:15     ` Greg Freemyer
2005-11-10 14:41       ` Tejun Heo
2005-11-10 15:26         ` linux
2005-11-10 17:32         ` Tejun Heo
2005-11-10 20:34           ` Greg Freemyer
2005-11-12  0:49             ` Greg Freemyer
2005-11-12  2:59               ` Tejun Heo
2005-11-13 10:19                 ` Tejun Heo
2005-11-14 23:30                   ` Greg Freemyer
2005-11-18  2:23                     ` sata_sil24 corruption FIXED by motherboard swap linux
2005-11-18 19:36                       ` sata_sil24 test support linux
2005-11-22  0:23                         ` linux
2005-11-22  1:52                           ` Tejun Heo [this message]
2005-11-11  2:16           ` sata_sil24 corruption details linux
2005-11-13  6:11             ` linux
2005-11-10 17:39         ` Jens Axboe
2005-11-10 20:27   ` Edward Falk
     [not found] <46377.137.32.101.32.1132172329.squirrel@www.stubbornroses.com>
     [not found] ` <437C0F2D.1000406@gmail.com>
2005-11-17  5:51   ` sata_sil24 test support James O. Rose, III
2005-11-17  7:01     ` Tejun Heo
2005-11-17 19:50       ` James Rose
  -- strict thread matches above, loose matches on Subject: below --
2005-11-17 22:58 James Rose
2005-11-18  0:35 ` James Rose

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=438279C2.6030002@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@horizon.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;
as well as URLs for NNTP newsgroup(s).