Red Hat Bugzilla – Bug 603051
/dev/changer symlink not created
Last modified: 2013-10-31 21:33:41 EDT
+++ This bug was initially created as a clone of Bug #600983 +++
Description of problem:
I have several systems with SCSI Medium Changers (auto-loaders, tape libraries) attached. Up to and including Fedora 12 udev would create a "/dev/changer" symbolic link pointing to the specific /dev/sg* device. After updating these systems to Fedora 13, these links are missing on all systems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot a system with a SCSI Medium Changer attached
2. Check that the console log contains output similar to this:
ch0: type #1 (mt): 0x0+1 [medium transport]
ch0: type #2 (st): 0x1+7 [storage]
ch0: type #3 (ie): 0x0+0 [import/export]
ch0: type #4 (dt): 0xf0+1 [data transfer]
ch0: dt 0xf0: READ ELEMENT STATUS failed
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch0: ... finished
ch 10:0:4:0: Attached scsi changer ch0
ch 10:0:4:0: Attached scsi generic sg6 type 8
3. Check if the /dev/changer link is there:
# ls -l /dev/chang*
ls: cannot access /dev/chang*: No such file or directory
Link is missing.
Normally, /lib/udev/rules.d/40-redhat.rules would detect that a SCSI type 8 device is there and create symlinks (in the example above, "/dev/changer" and "/dev/changer-sg6").
--- Additional comment from firstname.lastname@example.org on 2010-06-10 10:01:49 EDT ---
Does it work if you change SUBSYSTEM=="scsi_device" to SUBSYSTEM=="scsi_generic" in /lib/udev/rules.d/40-redhat.rules ?
--- Additional comment from email@example.com on 2010-06-10 15:42:54 EDT ---
Indeed - using SUBSYSTEM=="scsi_generic" works fine for me. Thanks a lot!
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.