Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932216AbWBRVmy (ORCPT ); Sat, 18 Feb 2006 16:42:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932210AbWBRVmy (ORCPT ); Sat, 18 Feb 2006 16:42:54 -0500 Received: from rtr.ca ([64.26.128.89]:17628 "EHLO mail.rtr.ca") by vger.kernel.org with ESMTP id S932206AbWBRVmx (ORCPT ); Sat, 18 Feb 2006 16:42:53 -0500 Message-ID: <43F794D8.7000406@rtr.ca> Date: Sat, 18 Feb 2006 16:42:48 -0500 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0 MIME-Version: 1.0 To: sander@humilis.net Cc: Jeff Garzik , Justin Piszcz , linux-kernel@vger.kernel.org, IDE/ATA development list Subject: Re: LibPATA code issues / 2.6.15.4 References: <43F1EE4A.3050107@rtr.ca> <43F58D29.3040608@pobox.com> <200602170959.40286.lkml@rtr.ca> <20060218204340.GA2984@favonius> In-Reply-To: <20060218204340.GA2984@favonius> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1507 Lines: 37 Sander wrote: > Mark Lord wrote (ao): >> On Friday 17 February 2006 03:45, Jeff Garzik wrote: >>> Submit a patch... >> You mean, something like this one? ... > [ 633.449961] md: md1: sync done. > [ 633.456070] RAID5 conf printout: > [ 633.456117] --- rd:9 wd:9 fd:0 ... > [ 1872.338185] ata6: translated op=0x2a ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00 > [ 1872.338239] ata6: status=0xd0 { Busy } > [ 5749.285084] ata8: translated op=0x2a ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00 > [ 5749.285138] ata8: status=0xd0 { Busy } > [ 5906.008461] ata6: translated op=0x2a ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00 > [ 5906.008515] ata6: status=0xd0 { Busy } ... > This is with 2.6.16-rc3, your patch, and running nine Maxtors disks > over onboard nForce4 and MV88SX6081 8-port SATA II PCI-X Controller (rev 09). > > for i in `seq 10` > do dd if=/dev/zero of=bigfile.$i bs=1024k count=10000 > done > md5sum bigfile.* > > The errors mostly seem to happen during the md5sum (not during the dd). SCSI opcode 0x2a is WRITE_10, so the errors are being reported in response to the writes to bigfile.$i. But these are different from the previously reported error status values -- I wonder why it's getting "Busy" back as a status here ?? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/