+++ This bug was initially created as a clone of Bug #759035 +++ commit a510b1c7f07ba750979ba2f213ebe261bcfc4de4 Author: Lukasz Dorau <lukasz.dorau> Date: Mon Nov 14 15:52:52 2011 +0100 imsm: fix: correct checking newly missing disks The problem occurs when RAID10 array under rebuild (after one disk fails) is assembled incrementally. Mdadm tries to start array just after adding the third disk and the volume is assembled incorrectly (in degraded state). The cause is that container_enough depends on newly missing disks which are checked incorrectly now. They should be checked using always the first map. Signed-off-by: Lukasz Dorau <lukasz.dorau> Signed-off-by: NeilBrown <neilb>
mdadm-3.2.3-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.3-2.fc16
Package mdadm-3.2.3-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.2.3-2.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0178/mdadm-3.2.3-2.fc16 then log in and leave karma (feedback).
mdadm-3.2.3-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.3-3.fc16
mdadm-3.2.3-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.