Red Hat Bugzilla – Bug 199033
Unable to specify parity
Last modified: 2007-11-30 17:07:26 EST
Description of problem:
When using mdadm to create a RAID5 array, it is impossible to specify the parity
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. You need some partitions or files setup with losetup
2. mdadm --create -l 5 -p la -n 3 /dev/md0 /dev/loop0 /dev/loop1 /dev/loop2
3. check the error message
mdadm: layout may only be sent once. Second value was la
Create the RAID array.
This is a software bug which has been fixed in newer versions of mdadm.
In the RH version, the bug can be seen on line 444 of mdadm.c. UnSet is a
constant but it is a positive number, to the test "layout >= 0" is always true.
Updated mdadm changes the test to be "layout != UnSet" which works.
Created attachment 132520 [details]
Fix testing for an unset parity (layout)
*** This bug has been marked as a duplicate of 197055 ***
But "You are not authorized to access bug #197055", so how would I ever know?
It doesn't really say anything more than this one (I can't change the
permissions to allow you to see the other bug, or else I would). Both reports
are legitimate and targetted for being fixed in the next update release.
*** Bug 197055 has been marked as a duplicate of this bug. ***
Thanks for the feedback.
The component of this request is planned to be updated in Red Hat enterprise
This enhancement 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.
We are updating mdadm to 1.12.0 for RHEL4.5 and that update solves this problem.
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.
Customer has been notified by the errata.
Internal Status set to 'Resolved'
Status set to: Closed by Tech
Resolution set to: 'RHEL 4.5'
This event sent from IssueTracker by lmacchia