Bug 130365
Summary: | Request to include EMC Celerra and iSCSI devices to the black list | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Heather Conway <conway_heather> |
Component: | kernel | Assignee: | Tom Coughlan <coughlan> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | kaufman_susan, perez-kolk_santiago, petrides, riel |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-18 13:27:48 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
Heather Conway
2004-08-19 17:19:25 UTC
looks good; can you send a patch with this to the linux-scsi mailinglist as well? Other question: the 2.6 kernel will use the report-luns command IF a device claims scsi3 compliance, if it doesn't claim that but still supports report-luns the prefered method is to blacklist this (instead of the SPARSE/LARGE lun flags). Can you find out if/how this device behaves in this respect ? Yes to both of your questions....thanks! Heather, I overlooked this for U4/U6 (sorry). Fortunately it is not necessary to update the whitelist for the Cisco software initiator. The driver does its own scanning, so the midlayer whitelist is ignored. I have tested sparsely-numbered LUNs on U4 with Celerra, and it works fine without the whitelist entries. I will add the "Celerra iSCSI" to the whitelist in U5/U7 anyway, just in case anyone tries to use the hardware initiators. They will presumably use the midlayer scanning. Would you please explain what you mean by "non-existing LUN" above? What are non-existing LUNs, and why do we need a whitelist entry for them? Heather, Can you look in to my question about "non-existing LUN" above? Tom A fix for this problem has just been committed to the RHEL3 U5 patch pool this evening (in kernel version 2.4.21-27.17.EL). An advisory 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. http://rhn.redhat.com/errata/RHSA-2005-294.html |