[8163] in linux-scsi channel archive
Re: recovery behaviour with 1 bad + 1 good drive (aic7xxx)
daemon@ATHENA.MIT.EDU (Ricky Beam)
Tue Feb 22 20:07:09 2000
Date: Tue, 22 Feb 2000 18:35:39 -0500 (EST)
From: Ricky Beam <jfbeam@bluetopia.net>
To: Dan Jones <djones@valinux.com>
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <38B314B2.9BD2853F@valinux.com>
Message-ID: <Pine.LNX.4.04.10002221831430.12259-100000@beaker>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 22 Feb 2000, Dan Jones wrote:
>Ricky Beam wrote:
>> That's a good asumption, but that _is_ why there's parity. I rank this
>> up there with your car's engine cutting off because the EEC detected
>> a sparkplug didn't fire.
>>
>Oh, goody, a metaphor war. I would liken SCSI parity to the
>catalytic converter warning light. When that comes on it is time
>to shut down the engine before serious damage results.
:-) Actually, the damage is already done when that light comes on. That's
also true for SCSI.
(My dad is a DOT mechanic [for 28 years.] I've seen melted cat. converters
before. You gotta wonder what kind of "wrong" can melt ceramic.)
--Ricky
BTW: This is the only controller I've ever seen to crash because of a parity
error.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
