Bug 151176
Summary: | linus bk after 2.6.11 has changed disk initialization timings | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jon Smirl <jonsmirl> |
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | davej, peterm, wtogami, zing |
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: | 2005-08-04 18:00:01 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
Jon Smirl
2005-03-15 17:49:47 UTC
After more discussion on lkml it looks like this is a problem with mkinitrd and udev. The script does udevstart followed by raidautorun. In my case the drive nodes are not all there and some of the volumes don't get added to the raid group. mkinitrd needs to be modified to provide some synchronization with udev. The sleep works because it lets udev run. The sleep is not a reliable solution since it may take more than 1 sec for udev to run. The change after 2.6.11 has altered things so that the raidautorun task now runs before udev. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. This is a problem with nash, initrd and udev. A new kernel isn't going to fix it. |