On Sunday July 17, dstrang@xxxxxxxxxxxxxx wrote: > Neil -- > > That worked, the device has been added to the array. Now, I think the next > problem is my own ignorance. It looks like your kernel is missing the following patch (dated 31st may 2005). You're near the bleeding edge working with version-1 superblocks (and I do thank you for being a guinea pig:-) and should use an ultra-recent kernel if at all possible. If you don't have the array mounted (or can unmount it safely) then you might be able to convince it to start the rebuild with by setting it read-only, then writable. i.e mdadm --readonly /dev/md0 mdadm --readwrite /dev/md0 alternately stop and re-assemble the array. NeilBrown ----------------------- Make sure recovery happens when add_new_disk is used for hot_add Currently if add_new_disk is used to hot-add a drive to a degraded array, recovery doesn't start ... because we didn't tell it to. Signed-off-by: Neil Brown <neilb@xxxxxxxxxxxxxxx> ### Diffstat output ./drivers/md/md.c | 2 ++ 1 files changed, 2 insertions(+) diff ./drivers/md/md.c~current~ ./drivers/md/md.c --- ./drivers/md/md.c~current~ 2005-05-31 13:40:35.000000000 +1000 +++ ./drivers/md/md.c 2005-05-31 13:40:34.000000000 +1000 @@ -2232,6 +2232,8 @@ static int add_new_disk(mddev_t * mddev, err = bind_rdev_to_array(rdev, mddev); if (err) export_rdev(rdev); + + set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); if (mddev->thread) md_wakeup_thread(mddev->thread); return err; - 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
