Bug 475384
| Summary: | RAID0 (Strip) – produces i/o errors on boot. Seems to be a Strip RAID system boots and work normally except for i/o errors on boot. | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Ed Ciechanowski <ed.ciechanowski> | ||||||||||||||
| Component: | mkinitrd | Assignee: | Hans de Goede <hdegoede> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Alexander Todorov <atodorov> | ||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||
| Priority: | low | ||||||||||||||||
| Version: | 5.3 | CC: | atodorov, borgan, cward, ddumas, fernando, hdegoede, heinzm, Jacek.Danecki, jane.lv, jgranado, jjarvis, jvillalo, keve.a.gabbert, krzysztof.wojcik, luyu, lvm-team, mgahagan, naveenr, nelhawar, pjones, rpacheco, syeghiay, tao | ||||||||||||||
| Target Milestone: | rc | Keywords: | OtherQA | ||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i386 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2009-09-02 11:15:34 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: | |||||||||||||||||
| Bug Depends On: | 471689, 485400 | ||||||||||||||||
| Bug Blocks: | 480792 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Ed Ciechanowski
2008-12-09 00:48:46 UTC
RAID0 (Strip) – produces i/o errors on boot. Seems to be a Strip RAID system boots and work normally except for i/o errors on boot. SEE ATTACHED .JPG If logs are needed let me know which ones. Is this a regression or critical error? It's getting very late to introduce new change into the release. Please make your case as soon as possible. Otherwise we'll be forced to defer to 5.4. If fixing for 5.4 is OK, please let me know that too. Can you also please post the error messages. Are the error messages seen in the installation at all? or just when the machine boots normally? Do you also see kernel messages saying that the partition table is busted? Created attachment 326370 [details]
Screen capture from fdisk -l
Created attachment 326371 [details]
df.txt from RAID0 system
I still need the boot messages. These are the most important ones. Also look into the installer itself and look for the same messages. thx. Created attachment 326382 [details]
output from the command "dmesg > bootmsg.log"
Yes this is what I see as well. Since this does not really prevent the booting of the machine. we will probably take out a relnote for this. Will come back with more info latter in the day. Created attachment 327910 [details]
Screen capture of RAID0 boot error
Tested RHEL5.3 RC1. Attached Log's and Screen Shot of boot errors.
Created attachment 327911 [details]
RAID0 logs from Install of RHEL5.3 RC1
Tested RHEL5.3 RC1. Attached Log's and Screen Shot of boot errors.
We tested RHEL 5.3 RC2. Issue still exist. I see the same errors as Ed detailed in comment 11. Do we know if these are actually harmful? It looks like the system's trying to read beyond the end of the disks. Gary: The errors will not prevent the booting of the machine. However, it would be nice to have it boot with no error messages. These errors are not info only, they are "real" but harmless. With the striped setup we use 2 disks as one large disk, but given this is sw raid the kernel sees the 2 separate disks too, and the first disk has a valid partition table spanning both disks, so when some tool tries to do something to those partitions we can get those errors as the partitions are bigger than one disk. This is completely harmless but probably very hard to fix, especially in the RHEL5 stream where we are more limited in the amount of change allowed. So assuming the kernel team agrees, we would like to address with a release note. I'll post a suggested release note in the BZ for review. The patches attached to BZ 485400 should provide a real fix avoiding the display of these error messages, and Heinz plans to incorporate them into 5.4. At that point we can validate this BZ and close it. We will leave the release note plan as a fallback in case there are unintended side effects from the patches that would prevent their addition to 5.4. Updating PM score. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. I have a question. Are you going to resolve this issue in RHEL5.4 or other release? Maybe version and status of this topic should be changed? This issue has been approved for 5.4.0, however the code is not yet complete so there is no guarantee at this point that it /will/ make it into the release. The status will be updated once a patch is available. This is not a kernel issue, but a userspace issue, the fix for this consists of 2 parts, first dmraid needs a few changes, which is tracked in bug 485400, and once that is done we need to make a few small changes to mkinitrd. So I'm changing the component of this bug to mkinitrd and assigning it to me. As soon as the new dmraid is available I'll make the necessary changes to mkinitrd. Hans, I'm waiting for flags to be set by PM/QE in order to be able to checkin and build a new dmraid version. Heinz has 485400 in Modified now. This is fixed in mkinitrd 5.1.19.6-49. ~~ Attention Partners RHEL 5.4 Partner Alpha Released! ~~ RHEL 5.4 Partner Alpha has been released on partners.redhat.com. There should be a fix present that addresses this particular request. Please test and report back your results here, at your earliest convenience. Our Public Beta release is just around the corner! If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. If you have verified the request functions as expected, please set your Partner ID in the Partner field above to indicate successful test results. Do not flip the bug status to VERIFIED. Further questions can be directed to your Red Hat Partner Manager. Thanks! Issue verified in RHEL5.4 Alpha with PASS result. Moving to VERIFIED as per comment #27 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-1345.html |