Red Hat Bugzilla – Bug 115345
need to whitelist IBM ESS to be scanned beyond LUN 0 by SCSI subsystem
Last modified: 2007-11-30 17:07:00 EST
Description of problem:
The IBM Enterprise Storage Server (aka Shark) has not been scanned
beyond LUN 0, although max_scsi_luns had been set appropriately in
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Load zfcp driver with module parameter "map=" containing more than
one FCP device address mapping, which make scsi_mod scan entire busses.
cat /proc/scsi/scsi -> only LUN 0 was detected
All LUNs specified in zfcp's "map=" paramter should be detected in the
Manually triggering SCSI device detection by means of
add-single-device works for each LUN and points out the underlying issue.
Created attachment 97569 [details]
patch that whitelists IBM ESS
The context is that we specifically asked IBM to whitelist ESS
in RHEL 3 (as opposed to enable sparse LUN scanning globally
in config-s390-generic) on Arjan's insistence.
Doug, do you want me to grab this?
Right, in the course of that discussion Pete's initial request sank
into oblivion. Mea culpa.
(Isn't anybody else at IBM testing this beast? :-\ )
*** This bug has been marked as a duplicate of 106392 ***
An errata 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 the 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.