Description of problem: dmraid is unable to activate a subset. This problem is aggravated by the fact that dmraid returns the name of the subset instead of the name of the superset when running the "dmraid -s -craidname" command. The output of "dmraid -s -craidname" is also used by mkinitrd this means that the system will not be able to activate any raid set at boot time. Version-Release number of selected component (if applicable): dmraid-1.0.0.rc13-6.1 with the patch to avoid the segmentation fault from BZ#427550 How reproducible: always Steps to Reproduce: 1. create a sparse device using dm loop and copy the metadata attached 2. # dmraid -s *** Group superset .ddf1_disks --> Active Subset name : ddf1_VERT02 size : 312237824 stride : 128 type : mirror status : ok subsets: 0 devs : 1 spares : 0 3. # /sbin/dmraid -s -craidname ddf1_VERT02 4. #try to activate the subset # dmraid -ay -i -p ddf1_VERT02 No RAID sets and with names: "ddf1_VERT02" 5. #using the name of the superset it works dmraid -ay -i -p .ddf1_disks ERROR: creating degraded mirror mapping for "ddf1_VERT02" # the error is ok as there is only one disk in the mirror Actual results: an error while trying to activate a subset Expected results: A subset activated Additional info: all the metadata and information to reproduce this issue are on BZ#427550
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.
User mceci's account has been closed
In package dmraid/1.0.0.rc13/13.el5
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/RHEA-2009-0078.html