Bug 515326

Summary: module load ordering problem in initrd for MRG RT 1.1 kernels (scsi_dh_rdac and qla2xxx)
Product: Red Hat Enterprise MRG Reporter: Clark Williams <williams>
Component: realtime-kernelAssignee: Luis Claudio R. Goncalves <lgoncalv>
Status: CLOSED CURRENTRELEASE QA Contact: David Sommerseth <davids>
Severity: medium Docs Contact:
Priority: low    
Version: DevelopmentCC: bhu, bugproxy, daniel.brnak, jvrao, lgoncalv, ovasik, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-06 15:03:59 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:
Attachments:
Description Flags
dmesg output of bad boot RHEL5.3+ MRG 101 none

Description Clark Williams 2009-08-03 18:16:20 UTC 
Description of problem:

On IBM blades and other systems using qla2xxx adapter the following description comes from IBM:

Unfortunately mkinitrd does not think that for dm root device scsi_dh_rdac is
needed. Hence in the stack of loaded modules scsi_dh_rdac is falling below the
qla2xxx. Because of this, there will be TONs of error messages for each lun on
each path. This causes long boot times, and sometimes random luns get only one
path.
Comment 1 Clark Williams 2009-08-03 18:39:37 UTC 
talk a bit with jvrao about this and it seems that if we use the --preload= option to mkinitrd things will work fine. We probably need to modify the specfile code for building the initrd to use --preload=scsi_dh_rdac whenever we see that qla2xxx is in use.
Comment 3 Clark Williams 2009-09-14 20:18:28 UTC 
*** Bug 491323 has been marked as a duplicate of this bug. ***
Comment 4 IBM Bug Proxy 2009-09-14 20:23:30 UTC 
Created attachment 360998 [details]
dmesg output of bad boot RHEL5.3+ MRG 101
Comment 5 IBM Bug Proxy 2010-03-31 16:41:29 UTC 
------- Comment From dvhltc.com 2010-03-31 12:40 EDT-------
This is likely addressed for SAN-only systems by updates available in RHEL5.5 from Bug 47343. We need to test a multipath SAN install on RHEL5.5.
Comment 6 IBM Bug Proxy 2010-03-31 22:20:43 UTC 
------- Comment From dvhltc.com 2010-03-31 18:17 EDT-------
I have tested a RHEL 5.5 GA (RC2) install on elm9m84 (LS21) using "mpath" on the kernel boot parameter and the system installed fine to an mpath device during the installer. RHEL 5.5 is required, so we still have to use workarounds for RHEL5.[1234], but we have a solution if a customer wants it : move to RHEL5.5. Marking as closed.