Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f5TKs7w16500 for linux-xfs-outgoing; Fri, 29 Jun 2001 13:54:07 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f5TKs6V16493 for ; Fri, 29 Jun 2001 13:54:06 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id WAA03532; Fri, 29 Jun 2001 22:54:04 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id WAA19326; Fri, 29 Jun 2001 22:54:01 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 9F04157306; Fri, 29 Jun 2001 23:03:58 +0200 (CEST) Received: from ch.sauter-bc.com (ppp01.cad.sba [10.1.249.1]) by mobile.sauter-bc.com (Postfix) with ESMTP id B4A7F25835; Fri, 29 Jun 2001 23:12:07 +0200 (CEST) Message-ID: <3B3CEAC9.D7A11BA@ch.sauter-bc.com> Date: Fri, 29 Jun 2001 22:53:29 +0200 From: Simon Matter X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i586) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos Cc: Andrew Klaassen , linux-xfs Subject: Re: XFS corruption on SoftRAID5 References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id f5TKs6V16498 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos schrieb: > On Fri, 29 Jun 2001, Andrew Klaassen wrote: > > > On Fri, Jun 29, 2001 at 12:28:06PM -0400, > > Martin K. Petersen wrote: > > > > > FWIW, almost all the XFS corruption bugs (with RAID or > > > otherwise) I've seen so far have been incorrect IDE hdparm > > > tuning or bad cabling. > > > > My question is really OT for this list, but how might one go > > about checking for bad cabling? Is there any software that can > > find it consistently? > > If the cable is not correct some cards will report it. > The promise controllers can report if a IDE cable is 80 pins or not. That's correct. But I think they just recognize whether it's 40 or 80 wires cable. Cables have always 40 pins, but 80 wires. > > > And the kernel sometimes also gives back errors. I have seen it once > already. The ATA66 and ATA100 standard have CRC checking for data sent CRC is what they should do, but I'm not shure they really do it always. > > over the cable. However forcing another a transfer mode is dangerous > and does net let a IDE interface set the correct mode on its own. > > I don't know if scsi has some form of CRC control.\ It has, it's not CRC but parity checking. Most controllers let you en/disable it. > > > Bye