[3045] in linux-scsi channel archive
Re: Dual-hosting SCSI and failure modes (was Re: RAID & unhappy scsi driver)
daemon@ATHENA.MIT.EDU (Andy Poling)
Tue Jan 6 10:52:43 1998
Date: Tue, 6 Jan 1998 10:41:17 -0500 (EST)
From: Andy Poling <andy@globalauctions.com>
To: Krzysztof Adamski <kadamski@netsurf.net>
cc: linas@linas.org, linux-raid@vger.rutgers.edu, linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.96.980105232014.2364J-100000@white.netsurf.net>
On Mon, 5 Jan 1998, Krzysztof Adamski wrote:
> > If you ask me, a bigger problem for recovery after a failed drive is the
> > current device naming scheme that could potentially result in *all* of the
> > remaining disks having different names after one is no longer available
> > (presently hot swapped out, powered down or otherwise totally unresponsive).
>
> There is a program called scsidev that eliminates this program, never used
> it but from the man:
>
> scsidev is a utility that is used to guarantee that the
> same device node can be used for the same scsi device, no
> matter what other scsi devices are added or removed from
> the scsi chain.
I checked this out (found at ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/,
though it's really not alpha) and it does indeed provide consistent naming
for SCSI devices (based on the hardware involved, like some other UNIX-like
OS's) in a /dev/scsi directory so long as you can get the system booted.
Tres kewl. Thanks for the tip Krzysztof!
-Andy
Global Auctions
http://www.globalauctions.com
