[5020] in linux-scsi channel archive
Re: Howto: rescan scsi bus after a hot swap ??
daemon@ATHENA.MIT.EDU (Michael Schwingen)
Wed Oct 28 13:15:29 1998
Date: Wed, 28 Oct 1998 16:23:26 +0100
From: Michael Schwingen <michaels@stochastik.rwth-aachen.de>
To: Drew Eckhardt <drew@Poohsticks.Org>
Cc: Michael Schwingen <michaels@stochastik.rwth-aachen.de>,
Marty Leisner <leisner@sdsp.mc.xerox.com>,
Chris Atenasio <chrisa@ultranet.com>,
Hardware Stuff <mrfixit@clouddancer.com>, linux-scsi@vger.rutgers.edu,
ncr53c810@Colorado.EDU
In-Reply-To: <199810242137.PAA15246@chopper.poohsticks.org>; from Drew Eckhardt on Sat, Oct 24, 1998 at 03:37:43PM -0600
On Sat, Oct 24, 1998 at 03:37:43PM -0600, Drew Eckhardt wrote:
> >From the last SCSI-II draft standard:
>
> 4.4.1.2. Input Characteristics
> ....
> It is recommended that SCSI devices with power off also meet the above IIL
> and IIH electrical characteristics on each signal.
>
> recommended != required. That this needs to be said implies that other
> characteristics may vary as well.
OK - I stand corrected.
> My current job involves disk based serial digital video recorders targeted
> at post production houses and broadcast television for play to air. Major
> networks wouldn't treat loss-of-signal from a bus glitch or the RST sledge
> hammer, so each of our 20 hot swap bays has its own SCSI bus.
>
> It depends on what sort of reliability you need or want.
Right. If you can tolerate the crash/reboot it hot-plugging should
eventually go wrong, (and you would have had to reboot anyway when powering
down), there does not seem to be a big risk, provided the cable stays
terminated.
However, in critical situations, you should look for different solutions.
cu
Michael
--
In the beginning there was nothing, which exploded.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
