linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: "J. Ryan Earl" <heretic@clanhk.org>
Cc: linux-ide@vger.kernel.org, RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: libata and md issues with 2.9.1-rc1
Date: Wed, 25 Aug 2004 08:53:12 +0400	[thread overview]
Message-ID: <412C1B38.7090401@wasp.net.au> (raw)
In-Reply-To: <412BC1C4.2060506@clanhk.org>

J. Ryan Earl wrote:
> Brad Campbell wrote:
> 
>> Just a heads up. I'm experiencing "issues" with 2.6.9-rc1 that don't 
>> occur with 2.6.5.
>>
>> I run a 10 disk raid-5 on 3xPromise SATA150 cards and a 2 disk raid-0 
>> on the on-board VIA chipset.
>> The 10 disks are Maxtor Maxline-II SATA drives and the raid-0 is a 
>> pair of WD2000JB drives with
>> Addonics SATA->PATA converters. 
> 
> 
> Did you try RAID-0 with the pair of Western Digital drives on the two 
> free Promise slots?  If that fails similarly, it might not be a libata 
> issue.

I thought about it. Given the drives are giving write errors when I write to /dev/md1 and not giving 
write errors when the raid is stopped and I write to the individual disks then it *must* be some 
issue with the hardware drivers.

If the block layer can submit a block to the driver that causes the drive to error out, then it's 
really a fault of the driver for trying to do something illegal.

Anyway, I have done a clone of the libata-2.6 bk tree and I'm trying to figure out how to extract 
all the individual csets between 2.6.6 and 2.6.7-rc1 so I can back them out 1 by 1 and see what 
caused the problem.

My other tack is to enable full SCSI debugging and compare the trace from 2.6.5 and 2.6.7-rc1 to see 
what is different.

I will give your suggestion a try when I get home tonight and fire it up on the extra promise channels.

Can anyone point me to a dummys guide to regression testing with BK? I read a great one by the WINE 
guys years ago on regression testing by date with CVS and it has proved immensely helpful over the 
years.

Regards,
Brad

      reply	other threads:[~2004-08-25  4:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 17:24 libata and md issues with 2.9.1-rc1 Brad Campbell
2004-08-24 17:40 ` Jeff Garzik
2004-08-24 17:50   ` Brad Campbell
2004-08-24 18:41   ` libata and md issues with 2.6.9-rc1 Brad Campbell
2004-08-24 22:31 ` libata and md issues with 2.9.1-rc1 J. Ryan Earl
2004-08-25  4:53   ` 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=412C1B38.7090401@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=heretic@clanhk.org \
    --cc=linux-ide@vger.kernel.org \
    --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).