DescriptionAndrius Benokraitis
2008-10-20 13:38:22 UTC
+++ This bug was initially created as a clone of Bug #467201 +++
Feature request:
Dynamic SCSI rescan functionality can be currently implemented by manually echoing values into the SCSI sysfs files. This is an extremely useful feature in enterprise scenarios, as a reload of the underlying driver(which does a SCSI rescan) is not practical as it is disruptive.
It would be ideal if the RHEL kernel provides a bundled SCSI rescan script which performs the following dynamic SCSI rescan functionalities:
1) Detect luns added to the host.
2) Remove luns from the host.
3) Resize existing luns on the host.
Version-Release number of selected component (if applicable):
RHEL 5.3.
--- Additional comment from dhorak on 2008-10-16 07:07:19 EDT ---
Are you looking for something like the rescan-scsi-bus.sh script from http://www.garloff.de/kurt/linux/scsidev/ ?
--- Additional comment from marting on 2008-10-16 07:39:56 EDT ---
Exactly.
This could be made a part of the sg3_utils package. Are there any plans to include this in future RHEL kernels?
--- Additional comment from dhorak on 2008-10-16 08:39:04 EDT ---
Please submit a request for enhancement via the standard support channel and let them bind the request with this bug.
I can add the script into Fedora on my own, so it will then appear in RHEL 6.
--- Additional comment from andriusb on 2008-10-16 12:53:48 EDT ---
Dan - NetApp is a formal engineering Partner and therefore this bugzilla will serve as the official feature request I'll monitor (being their assigned partner manager).
Comment 1Andrius Benokraitis
2008-10-20 13:40:43 UTC
The RHEL 5.4 bug for this issue can be found at bug 467201.
I have cloned this bug for Fedora Rawhide and made it block this bug. Dependency on the RHEL 5.4 original bug (auto created during cloning) is removed.
NetApp has verified bug 538787, so marking this one as verified, too.
Comment 9releng-rhel@redhat.com
2010-11-11 14:58:43 UTC
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.