On Fri, May 04, 2012 at 03:05:48PM +0200, Jes Sorensen wrote: > Hi, > > Could you please apply this one to linux-stable 3.3? It fixes a case > where a raid5 isn't actually being checked when requested explicitly, > which could result in catastrophic data failure. > > git commit from Linus tree. > > Thanks, > Jes > > commit c6d2e084c7411f61f2b446d94989e5aaf9879b0f > Author: majianpeng <[email protected]> > Date: Mon Apr 2 01:16:59 2012 +1000 > > md/raid5: Fix a bug about judging if the operation is syncing or > replacing > > When create a raid5 using assume-clean and echo check or repair to > sync_action.Then component disks did not operated IO but the raid > check/resync faster than normal. > Because the judgement in function analyse_stripe(): > if (do_recovery || > sh->sector >= conf->mddev->recovery_cp) > s->syncing = 1; > else > s->replacing = 1; > When check or repair,the recovery_cp == MaxSectore,so syncing equal zero > not one. > > This bug was introduced by commit 9a3e1101b827 > md/raid5: detect and handle replacements during recovery. > so this patch is suitable for 3.3-stable. > > Cc: [email protected] > Signed-off-by: majianpeng <[email protected]> > Signed-off-by: NeilBrown <[email protected]>
Very wierd, I wonder how this slipped through my scripts and I didn't see it previously? Anyway, thanks for pointing it out, now applied. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
