Bug 221556
| Summary: | Raid mirroring not activated | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bruce Orchard <orchard> | ||||||||||||||
| Component: | anaconda | Assignee: | Peter Jones <pjones> | ||||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | |||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | 6 | CC: | jonstanley, triage | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i686 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | bzcl34nup | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2008-04-05 01:26:36 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
Bruce Orchard
2007-01-05 03:51:05 UTC
Created attachment 144879 [details]
Output from dmraid -n
Created attachment 144880 [details]
Output from mount
Created attachment 144881 [details]
Output from vmstat -d
Created attachment 144882 [details]
init from initrd
Created attachment 144883 [details]
/etc/fstab
Created attachment 144953 [details]
grub device.map generated by anaconda
No change in Fedora 7 It looks like the source of the problem is the + in the raid group name. Here is the output from dmsetup: [root@localhost fedora]# dmsetup table isw_dgjddddaee_Drives0+13: 0 20482875 linear 253:1 290824695 isw_dgjddddaee_Drives0+1: 0 312494080 mirror core 2 131072 nosync 2 8:0 0 8:16 0 isw_dgjddddaee_Drives0+12: 0 249858945 linear 253:1 40965750 isw_dgjddddaee_Drives0+11: 0 40965687 linear 253:1 63 live-rw: 0 8388608 snapshot 7:121 7:119 P 8 The + causes problems in resolve_dm_name (in /etc/init.d/functions) when the name is used as a pattern in awk. The + is interpreted by awk as meaning "match one or more of the preceeding character", not match itself. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers I changed the name of the raid group to remove the +. That made it work. thanks for the update, closing bug |