Bug 236891
| Summary: | dmraid -r -E bus error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Ask Bjørn Hansen <ask> | ||||
| Component: | dmraid | Assignee: | Ian Kent <ikent> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.0 | CC: | agk, dwysocha, heinzm, ikent, mbroz, prockai | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | RHBA-2008-0475 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-21 17:20:56 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: | |||||||
| Bug Blocks: | 363331 | ||||||
| Attachments: |
|
||||||
|
Description
Ask Bjørn Hansen
2007-04-18 10:08:49 UTC
It's been a while and there doesn't seem to have been any activity on this bug. Is this still a problem? If it is could you post the files created by "dmraid -rD" and also send the standard output to a file and post that as well please. Otherwise just close the bug. Ian Hi Ian, After a few weeks of not hearing back I got the server reconfigured to get rid of the dmraid stuff and reinstalled RHEL (If I recall correctly then it could be done on the actual console, the idiotic Intel RAID bios didn't do console redirection). All the data I have is included above. - ask (In reply to comment #2) > Hi Ian, > > After a few weeks of not hearing back I got the server reconfigured to get rid of the dmraid stuff and > reinstalled RHEL (If I recall correctly then it could be done on the actual console, the idiotic Intel RAID bios > didn't do console redirection). > > All the data I have is included above. Yes, it makes it hard when nobody can get to look into the issue in a sensible time. Unfortunately, to work out what's going on I would need the output from the command I mentioned above. Without it I'd just be guessing and that's rarely ever useful. So I'm stuck now. I'll see if Heinz has any suggestions but I don't hold much hope. Sorry. Ian Using a test environment I got from Heinz Mauelshagen I was able to reliably cause a SEGV with "dmraid -r -E". This may not be what was seen here but since we no longer have the setup to test I think we should just fix the problem I have found. I suspect there is another problem lurking here as there were two raid devices in this setup but the problem I found is triggered when the configuration has only one raid device. The above report does hind that that the configuration may actually have had only one device in it when the error occurred but I can't be sure. The problem occurs when the on disk meta data configuration contains one raid device only (one block only) then the isw module determines there are no extended attributes and extra space isn't allocated during the meta data read. However, the meta data write function fails to check whether the extra space is present before copying the meta data and SEGVs when trying to write it to the non existent memory. Ian Created attachment 233921 [details]
Patch to avoid writting to non-existent memory during metadata erase
Hi Ian, That sounds right actually. The box I worked on had 2 or 4 drives, but I think only one of the drives had problems getting the dmraid data removed, so from the perspective of dmraid there might only have been one. I don't use dmraid, but I'm glad that it got fixed! - ask 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. 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 the 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-2008-0475.html |