[3040] in linux-scsi channel archive
Re: Dual-hosting SCSI and failure modes (was Re: RAID & unhappy scsi driver)
daemon@ATHENA.MIT.EDU (Krzysztof Adamski)
Mon Jan 5 23:29:39 1998
Date: Mon, 5 Jan 1998 23:23:59 -0500 (EST)
From: Krzysztof Adamski <kadamski@netsurf.net>
To: Andy Poling <andy@globalauctions.com>
cc: linas@linas.org, linux-raid@vger.rutgers.edu, linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.96.980105225109.16349F-100000@roadrunner.realbig.com>
> 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. The need for this tool arose because
device numbers are assigned dynamicly at boot time, and if
a new disk were added to the system (or if some disk
didn't spin up), then fixed device nodes would cause the
wrong filesystems to be mounted, checked, etc. This can
also result in security holes, as some device nodes may
have permissions that allow general users access to the
raw device, and if the mappings were to change, users
would be able to access different devices.
Krzysztof
