Bug 759035

Summary: imsm: fix: correct checking newly missing disks
Product: [Fedora] Fedora Reporter: Jes Sorensen <Jes.Sorensen>
Component: mdadmAssignee: Jes Sorensen <Jes.Sorensen>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: agk, dledford, Jes.Sorensen, mbroz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 759036 759037 (view as bug list) Environment:
Last Closed: 2012-05-04 16:11:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 759036, 759037    

Description Jes Sorensen 2011-12-01 10:02:01 UTC
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>

Comment 1 Jes Sorensen 2012-01-05 13:37:22 UTC
Fix included in mdadm-3.2.3