I'm using SuSE 10 and need to have my scsi devices maintain the same name. They are actually SATA drives attached to a 3Ware 9000 controller. One drive rarely gets removed and the others are routinely removed and others plugged in their place or the system is booted without them. By default, the drives get device names of /dev/sda, sdb, sdc, etc., based on what port they're plugged into. If nothing is in port 0, the drive in port 1 gets sda. I would like for it to get sdb like it does when a drive is also attached to port 0. I'm a bit confused about udev, hotplug, scsidev and their interactions in spite of reading various man pages and manuals. After playing around with udevinfo I created this rule in /etc/udev/49-udev.rules: US="scsi", SYSFS{path}="pci-0000:00:09.0-scsi-0:0:0:0", NAME="sdb" but it had no effect. The drive in port 1 still got sda. I enabled boot.scsidev and the device /dev/scsi/sdh0-0c0i0l0 was created. However, /dev/sda was still created and assigned to the same drive. Am I supposed to get used to dealing with devices like /dev/scsi/sdh0-0c0i0l0 or is there some way to get persistent /dev/sda, sdb, etc. devices? Jason Joines =================================
Jason Joines wrote:
I'm using SuSE 10 and need to have my scsi devices maintain the same name. They are actually SATA drives attached to a 3Ware 9000 controller. One drive rarely gets removed and the others are routinely removed and others plugged in their place or the system is booted without them. By default, the drives get device names of /dev/sda, sdb, sdc, etc., based on what port they're plugged into. If nothing is in port 0, the drive in port 1 gets sda. I would like for it to get sdb like it does when a drive is also attached to port 0.
I'm a bit confused about udev, hotplug, scsidev and their interactions in spite of reading various man pages and manuals. After playing around with udevinfo I created this rule in /etc/udev/49-udev.rules: US="scsi", SYSFS{path}="pci-0000:00:09.0-scsi-0:0:0:0", NAME="sdb" but it had no effect. The drive in port 1 still got sda.
I enabled boot.scsidev and the device /dev/scsi/sdh0-0c0i0l0 was created. However, /dev/sda was still created and assigned to the same drive. Am I supposed to get used to dealing with devices like /dev/scsi/sdh0-0c0i0l0 or is there some way to get persistent /dev/sda, sdb, etc. devices?
Jason Joines =================================
Which SCSI module are you using? What does your /proc/scsi tree look like? Your persistent binding is normally configured along with the SCSI module in /etc/modprobe.conf. Thanks, LDB
LDB wrote:
Jason Joines wrote:
I'm using SuSE 10 and need to have my scsi devices maintain the same name. They are actually SATA drives attached to a 3Ware 9000 controller. One drive rarely gets removed and the others are routinely removed and others plugged in their place or the system is booted without them. By default, the drives get device names of /dev/sda, sdb, sdc, etc., based on what port they're plugged into. If nothing is in port 0, the drive in port 1 gets sda. I would like for it to get sdb like it does when a drive is also attached to port 0.
I'm a bit confused about udev, hotplug, scsidev and their interactions in spite of reading various man pages and manuals. After playing around with udevinfo I created this rule in /etc/udev/49-udev.rules: US="scsi", SYSFS{path}="pci-0000:00:09.0-scsi-0:0:0:0", NAME="sdb" but it had no effect. The drive in port 1 still got sda.
I enabled boot.scsidev and the device /dev/scsi/sdh0-0c0i0l0 was created. However, /dev/sda was still created and assigned to the same drive. Am I supposed to get used to dealing with devices like /dev/scsi/sdh0-0c0i0l0 or is there some way to get persistent /dev/sda, sdb, etc. devices?
Jason Joines =================================
Which SCSI module are you using? What does your /proc/scsi tree look like? Your persistent binding is normally configured along with the SCSI module in /etc/modprobe.conf.
Thanks,
LDB
I'm using 3w-9xxx. # ls -Rl /proc/scsi /proc/scsi: total 0 dr-xr-xr-x 3 root root 0 Dec 22 13:21 . dr-xr-xr-x 94 root root 0 Dec 21 09:11 .. -r--r--r-- 1 root root 0 Dec 22 13:21 device_info -r--r--r-- 1 root root 0 Dec 22 13:21 scsi dr-xr-xr-x 2 root root 0 Dec 22 13:21 sg /proc/scsi/sg: total 0 dr-xr-xr-x 2 root root 0 Dec 22 13:21 . dr-xr-xr-x 3 root root 0 Dec 22 13:21 .. -rw-r--r-- 1 root root 0 Dec 22 13:21 allow_dio -r--r--r-- 1 root root 0 Dec 22 13:21 debug -rw-r--r-- 1 root root 0 Dec 22 13:21 def_reserved_size -r--r--r-- 1 root root 0 Dec 22 13:21 device_hdr -r--r--r-- 1 root root 0 Dec 22 13:21 device_strs -r--r--r-- 1 root root 0 Dec 22 13:21 devices -r--r--r-- 1 root root 0 Dec 22 13:21 version Do you have an example modprobe.conf that accomplishes something similar? Thanks, Jason ===========
participants (2)
-
Jason Joines -
LDB