Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:1872
Description of problem: Version-Release number of selected component (if applicable): From sg3_utils-1.28-6.el6 In sg3_utils-1.28-5, `rescan-scsi-bus.sh --luns=1` will only rescan luns numbered 1, which is expected. Starting from sg3_utils-1.28-6, `rescan-scsi-bus.sh --luns=1` will scan all luns, which we don't like. How reproducible: Steps to Reproduce: 1. Attach multiple SCSI disk to a RHEL6 VM. 2. Run `rescan-scsi-bus.sh --luns=1` Actual results: It scan all luns. ~]# ./rescan-scsi-bus-test2.sh --luns=1 which: no multipath in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) Scanning SCSI subsystem for new devices Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 1 Scanning for device 0 0 0 0 ... OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: QEMU Model: QEMU DVD-ROM Rev: 1.5. Type: CD-ROM ANSI SCSI revision: 05 Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 1 Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 1 Scanning for device 2 0 0 0 ... OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: QEMU Model: QEMU HARDDISK Rev: 1.5. Type: Direct-Access ANSI SCSI revision: 05 Scanning for device 2 0 0 1 ... OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 01 Vendor: QEMU Model: QEMU HARDDISK Rev: 1.5. Type: Direct-Access ANSI SCSI revision: 05 0 new or changed device(s) found. 0 remapped or resized device(s) found. 0 device(s) removed. Expected results: Should only scan lun 1. ~]# ./rescan-scsi-bus-test1.sh --luns=1 Host adapter 0 (ata_piix) found. Host adapter 1 (ata_piix) found. Host adapter 2 (virtio_scsi) found. Scanning SCSI subsystem for new devices Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 1 Scanning host 1 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 1 Scanning host 2 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 1 Scanning for device 2 0 0 1 ... OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 01 Vendor: QEMU Model: QEMU HARDDISK Rev: 1.5. Type: Direct-Access ANSI SCSI revision: 05 0 new device(s) found. 0 device(s) removed. Additional info: This unexpected behavior was introduced by: * Tue Jun 24 2014 Dan Horák <dhorak> - 1.28-6 - update rescan-scsi-bus.sh to 1.57 (#857200) - Resolves: #857200