Bug 464636
| Summary: | scsi scan not waiting long enough | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Bill Peck <bpeck> | ||||||
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 5.3 | CC: | abourne, borgan, clalance, cmeadors, ddumas, jburke, maurizio.antillon, syeghiay, traxtopel, vbenes | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-01-20 22:12:46 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
Bill Peck
2008-09-29 19:15:06 UTC
Do you still have this problem with mkinitrd-5.1.19.6-37 ? Created attachment 323127 [details]
Possible fix
Can you please test with the affixed patch?
Brock, Bill, Arlinton - we dont have this hardware or anything like it, can one of you please check that this patch fixes things for you? If possible, we'd like to get this reviewed and submitted for Snap4 which is Wednesday ... Thanks I don't have the hardware either, will ping bpeck about this issue ... Regards, Brock What am I supposed to do with the patch? If you provide me an updates.img I can work with that. Use the repo at http://people.redhat.com/pjones/mkinitrd-464636/ during installation. Did it work, Bill? If so, we can get this patch in for Wednesday Snap5... The job failed but it looks like it was because of multi-path. Looking at the log it does show the disks being loaded before scanning for the Volume Groups. I'm attaching the log for you to make a decision with. Created attachment 324488 [details]
console log bootup after install
This should be fixed in 11.1.2.160-1 . I noticed a difference in the latest snapshot regarding this behavior. I am seeing "Could not detect stabilization, waiting 10 seconds" just before the drives are scanned. I was not seeing this before on the same hardware. I tried to time the pause in the 124 kernel that happens at the same place as this new error message and it seems like it takes the same amount of time. So this is just a new error message. I just wanted to make sure that the effects on other systems that did not have problems was recognized. latest snapshot being 5 with kernel 125 I'm also seeing the "Could not detect stabilization, waiting 10 seconds" message, and it is most certainly taking longer on my hardware to initialize. With the 5.2 mkinitrd, it took around 4-5 seconds; with this mkinitrd, it now takes that + 10 seconds. (I'm switching to FAILS_QA at the moment; not sure if that is the right BZ state) Chris Lalancette Chris and Cameron, did it wait long enough for your scsi disks to be detected? The "Could not detect stabilization" message is expected behavior and release noted already, a Fedora patch was backported that waits for a maximum time. If we wait long enough for the disks to be detected, that solves the reported problem. Yes, it did, but as I said, it adds an additional 10 second wait that wasn't there before (I never saw this particular bug on this hardware before). I guess the thing is: either we are going to unconditionally wait 10 seconds (which is bad behavior in my opinion, but maybe the only way to fix the bug), or we aren't. If we are going to do the unconditional wait, then no message is necessary. Chris Lalancette It's not always a 10 second wait, that's the max. But no way around the wait until we get a kernel change, and that won't happen in rhel5. So per dmaley/dmair, we're going to remove the informational message in Snap6. Message removed in mkinitrd-5.1.19.6-42 . *** Bug 475943 has been marked as a duplicate of this bug. *** *** Bug 475965 has been marked as a duplicate of this bug. *** 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 therefore 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/RHBA-2009-0237.html |