Description of problem: The /dev/disk/by-path symlink for iSCSI LUNs fails to include the lun number, so all iSCSI luns from a particular target end up with the same clashing symlink. Version-Release number of selected component (if applicable): udev-095-14.9.el5 How reproducible: Always Steps to Reproduce: 1. Login to an iSCSI target which has multiple luns 2. Examine /dev/disk/by-path 3. Actual results: Only a single link per target # ls /dev/disk/by-path/ ip-192.168.122.170:3260-iscsi-demo-tgt-a ip-192.168.122.170:3260-iscsi-demo-tgt-b Expected results: One link per LUN: # ls /dev/disk/by-path/ip* /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-a-lun-1 /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-a-lun-2 /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-a-lun-3 /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-a-lun-4 /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-a-lun-5 /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-b-lun-1 /dev/disk/by-path/ip-192.168.122.170:3260-iscsi-demo-tgt-b-lun-2 Additional info: Works correctly on Fedora 8...
Created attachment 290899 [details] Fix iSCSI /dev/disk/by-path links to include LUN information This patch is basically a diff of the /lib/udev/path_id between RHEL-5 and F-8 for the iSCSI bits. With this patch applied RHEL-5 operates correctly for iSCSI LUNS
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Granting Devel ACK. Read ya, Phil
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0076.html