Bug 1380346
Summary: | `rescan-scsi-bus.sh --luns` scans all luns. | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Wu Siu Wa <siwu> | |
Component: | sg3_utils | Assignee: | Gris Ge <fge> | |
Status: | CLOSED ERRATA | QA Contact: | guazhang <guazhang> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 6.9 | CC: | cww, djez, jkurik, knoha, rhandlin | |
Target Milestone: | rc | Keywords: | Patch, Regression, Reopened | |
Target Release: | 6.10 | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | sg3_utils-1.28-13.el6 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1380744 (view as bug list) | Environment: | ||
Last Closed: | 2018-06-19 05:11:46 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1380744, 1507140 |
Description
Wu Siu Wa
2016-09-29 11:27:30 UTC
Thanks for report, I believe this was reported and fixed upstream as well - https://github.com/hreinecke/sg3_utils/issues/3 ... https://github.com/hreinecke/sg3_utils/pull/4/commits/66af0c64749682e5d5dfcb372e2e521b5a583794 patch is supposed to correct this wrong behaviour. Can you please check this and confirm the fix if possible? The patch would be: diff --git a/scripts/rescan-scsi-bus.sh b/scripts/rescan-scsi-bus.sh index fad4868..bbe2228 100755 --- a/scripts/rescan-scsi-bus.sh +++ b/scripts/rescan-scsi-bus.sh @@ -715,7 +715,16 @@ searchexisting() else match=1 fi - test $match -eq 1 && doreportlun + + test $match -eq 0 && continue + + if [ -z "$lunsearch" ] ; then + doreportlun + else + for lun in $lunsearch ; do + dolunscan + done + fi done } Hello I have tested sg3_utils-1.28-13.el6 and passed, move to verified 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 |