Bug 113731
| Summary: | "scsi add-single-device" and "scsi remove-single-device" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Wendy Cheng <nobody+wcheng> |
| Component: | kernel-utils | Assignee: | Jim Paradis <jparadis> |
| Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | peterm, tao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-09-07 20:28:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Wendy Cheng
2004-01-16 21:49:20 UTC
see http://download.qlogic.com/drivers/23292/readme.txt --- 9.6 How To Force Rescan Of Devices ---------------------------------- Starting from driver version v6.06.00b12 there is support for the mechanism which allows the user to force the driver to do re-scan of the devices to allow a new device to be added. This triggers the driver to initiate lun discovery process. To do this from the command line: # echo "scsi-qlascan" > /proc/scsi/<driver-name>/<adapter-id> (qlogic driver re-scans) Where <driver-name> can be either one : qla2100/qla2200/qla2300 <adapter-id> is the instance number of the HBA. Once that has been done , user then can force the scsi mid layer to do its own scan and build the device table entry for the new device: # echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi (scsi mid layer re-scans) Where "0 1 2 3" is replaced by your "Host Channel Id Lun". The scanning has to be done in the above mentioned order. First the driver (qla2300/qla2200 driver etc) and then the Linux scsi mid layer (i.e. OS scan) later. At this time any fix for this is beyond the scope of RHEL2.1 support status (only critical security fixes are being accepted). Since there is a known workaround, no other fix will be implemented. |