[3446] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: Name assignation of scsi devices

daemon@ATHENA.MIT.EDU (Selva Nair)
Wed Mar 4 08:56:25 1998

Date: 	Wed, 4 Mar 1998 22:14:03 +0900 (JST)
From: Selva Nair <selva@sqdp.trc-net.co.jp>
To: Mr LEROY christophe <leroy@meg.fr>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <mxMail.9834134530@meg.meg.fr>


scsi devices are named in the order (and optionally in the reverse order
if the driver supports it) of the scsi id isn't it? So if you do not
change the id should there be any problem? Some drivers also allow reverse
order probing, I guess.

Selva
----------
On Wed, 4 Mar 1998, Mr LEROY christophe wrote:

   Assigned devices names to scsi drives:
   
   When linux boots, it assignes dynamically names to scsi devices:
   - When you add a disk, all your disks whose target is upper are changed, so you
   have to modify you /etc/fstab, /etc/mdtab and /etc/raid?.conf
   because sdc has become sdd and so on


   One can say it is not important as you dont change disks often, but
   
   When a disk is on fire, and you have configured your linux with raid1 to
   continue to work in such a situation, it doesn't work because on reboot,
   your defectuous disk hasn't been detected so drives designations have changed
   and 
   mdadd doesn't work
   
   So I think it would be better to have fixed scsi device named as you have
   for IDE (hdc is always the second IDE master, even if there is no first IDE
   slave
   
   Christophe Leroy
   
   
   -
   To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
   the body of a message to majordomo@vger.rutgers.edu
   


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post