[9386] in linux-scsi channel archive
Re: shared SCSI buses
daemon@ATHENA.MIT.EDU (Matthias Andree)
Mon Aug 14 09:04:18 2000
Date: Mon, 14 Aug 2000 15:01:29 +0200
From: Matthias Andree <matthias.andree@gmx.de>
To: linux-scsi@vger.rutgers.edu
Message-ID: <20000814150129.E6878@lxMA.mediaways.net>
Mail-Followup-To: linux-scsi@vger.rutgers.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001701c00448$6ea77ac0$0da4b3d4@sergv>; from SVichik@storeage.com on Sat, Aug 12, 2000 at 12:31:01 +0200
On Sat, 12 Aug 2000, StoreAge wrote:
> I'm new to this field, but because I need to face this problem in the
> real world, I want to contribute to this discussion my experience and
> some questions.
>
> Fact #1 : Reset wars do happen. Booting linux system in
> multi-initiator environment often cause infinite reset-bus loop, even
> with only one linux system - others are NT and Sun. Sometimes it is
> ended with crash of all hosts. ( including NT and Sun). Almost every
> time, some period of time after linux boot all hosts are loosing
> network view.
> Fact #3: This behavior isn't seems to be related to low-level driver :
> We have tested 2 QLogic HBA drivers and one Emulex HBA driver.
This is a matter of those HBA drivers, as to what Kurt has written. He
can speak of the tmscsi (DC-390) and dc-3x5 drivers. I see reset wars
with Adaptec 7xxx (2842, 2940AU and UW, mostly) as well, though not on
SYM53C8xx (Tekram DC-390U).
> If bus reset do happen, it shouldn't affect IO operations from high
> level driver point of view, because retries should handle it anyway ?
Yes, they "should not".
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
