From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Description of problem:
If you have a raid1 mirror that fails, you can remove the drive and
replace it, but when you go to add that drive back, it always goes in
with a delayed resync (it will wait until the next reboot).
Furthermore, if you have other arrays that also use that drive and you
try to sync them (raid1 or otherwise), they too will be delayed
because of the raid1 array and if you reboot the system, you can then
get fs corruption because that delayed status isn't properly handled.
This is fixed in 2.6.8-rc1 by two patches from Neil Brown:
o Fix raid1 read_balancing code
o md: Fix up handling for read error in raid1
If these could make their way into an errata release sooner rather
than later, it would save a lot of grief working with RAID arrays.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. setup raid1
2. hard-fail out a drive
3. try to readd drive
Actual Results: Drive goes in with a delayed resync
Expected Results: Drive beings resyncing immediately
This was fixed in subsequent erratas which contained patches from Neil