Bug 101058 - MSA1000 disk array needs one line added to scsi_scan.h
MSA1000 disk array needs one line added to scsi_scan.h
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
2.1
ia64 Linux
high Severity medium
: ---
: ---
Assigned To: Tom Coughlan
Brian Brock
HP says QU3/IPF show stopper
:
Depends On:
Blocks: 87937
  Show dependency treegraph
 
Reported: 2003-07-28 16:42 EDT by Micah Parrish
Modified: 2007-11-30 17:06 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-26 12:28:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Micah Parrish 2003-07-28 16:42:36 EDT
Description of problem:
The MSA1000 disk array uses non-consecutive lun numbering and needs the
following line added to scsi_scan.h:
{"COMPAQ", "MSA1000", "*", BLIST_FORCELUN},

The line was added to the kernel.org sources sometime between 2.4.18 and 2.4.20.

Our customers need to be able to install their array without recompiling the
kernel, so could you please get that line into a AS2.1 errata kernel somehow?
Comment 1 Larry Troan 2003-07-30 12:30:25 EDT
ISSUE TRACKER  26348 opened as sev 1
Comment 2 Larry Troan 2003-07-30 12:34:00 EDT
IS THIS AS 2.1 OR TAROON (RHEL3) IPF. ISSUE TRACKER SAYS 3 BUT YOUR DESCRIPTION
IMPLIES 2.1........ (Bug needs to be NEEDINFO)
Comment 3 Micah Parrish 2003-07-30 12:50:08 EDT
This is fixed in the RHEL3 kernel due to being fixed in the kernel.org sources.
 What we need is the one line fix to be included in the next errata kernel for
2.1AS.
Comment 4 Larry Troan 2003-07-30 14:25:29 EDT
Confirmed that this is an AS2.1 QU2 bug with fix required in U3.
Comment 5 Larry Troan 2003-08-01 17:17:36 EDT
BLOCKER BUG.
Comment 6 Micah Parrish 2003-08-26 12:28:25 EDT
This has been fixed in the 2.4.18-3.37 errata kernel, so I am closing this bug now.

Note You need to log in before you can comment on or make changes to this bug.