This test is overly specific, and misses raid10. Assume all levels >= 1 might need reconstruction instead. Signed-off-by: Neil Brown <neilb@xxxxxxxxxxxxxxx> ### Diffstat output ./drivers/md/md.c | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff ./drivers/md/md.c~current~ ./drivers/md/md.c --- ./drivers/md/md.c~current~ 2005-02-18 11:11:11.000000000 +1100 +++ ./drivers/md/md.c 2005-02-18 11:11:17.000000000 +1100 @@ -1478,9 +1478,8 @@ static int analyze_sbs(mddev_t * mddev) - if ((mddev->recovery_cp != MaxSector) && - ((mddev->level == 1) || - ((mddev->level >= 4) && (mddev->level <= 6)))) + if (mddev->recovery_cp != MaxSector && + mddev->level >= 1) printk(KERN_ERR "md: %s: raid array is not clean" " -- starting background reconstruction\n", mdname(mddev)); - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
