Bug 65606

Summary:	7.2 to 7.3 upgrade breaks qlogic scsi lun visibility
Product:	[Retired] Red Hat Linux	Reporter:	Anthony Clark <aclrk>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.3	CC:	goodin
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:39:38 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 Anthony Clark 2002-05-28 14:20:41 UTC

Description of Problem:
In rh 7.2, loading the qla2x00 driver and enabling scsi lun scanning in the 
kernel (via recompiling the kernel) allows rh to 'see' all the devices 
attached to the server via a fibre channel device that maps devices to scsi 
luns.
Trying to do the same with rh 7.3 does not work, none of the >0 luns are 
scanned, and the 0 lun devices are reported incorrectly.

How Reproducible:
With a qlogic 2200 fibre adapter connecting to a Dell PowerVault 136T tape 
library:  install a base 7.2 server. copy the i686-smp config file to .config 
in /usr/src/linux-2.4.  run make menuconfig and enable lun scanning.  build 
and install the kernel, reboot to 'see' the new non-lun 0 devices.
With the same system, install (don't upgrade) rh 7.3 and try the same steps.  
The system doesn't see any devices with a lun higher than 0.

Additional Information:
We've gone back to using 7.2 on the 3 servers that use fibre to connect to the 
library, but our upgrade path doesn't exist :-(

Comment 1 Bugzilla owner 2004-09-30 15:39:38 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/