Date: Fri, 29 Jun 2001 22:29:56 +0200 (CEST)
From: Seth Mos <knuffie@xs4all.nl>
To: Andrew Klaassen <ak@dkp.com>
cc: linux-xfs <linux-xfs@oss.sgi.com>
Subject: Re: XFS corruption on SoftRAID5
In-Reply-To: <20010629130641.B782@dkp.com>
Message-ID: <Pine.BSI.4.10.10106292212520.26374-100000@xs3.xs4all.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

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.

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
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.\

Bye