Mike Tran <mhtran@us.ibm.com> wrote:
| I have been experiencing the same problem on my test machine. I found
| out that the resync terminated early because of MD_RECOVERY_ER R bit set
| by raid1's sync_write_request(). I don't understand why it fails the
| sync when all the writes already completed successfully and quickly. If
| there is a need to check for "nowhere to write this to" as in 2.4.x
| kernel, I think we need a different check.
|
| The following patch for 2.6.0-test8 kernel seems to fix it.
|
| --- a/raid1.c 2003-10-17 16:43:14.000000000 -0500
| +++ b/raid1.c 2003-10-22 11:57:59.350900256 -0500
| @@ -841,7 +841,7 @@
| }
|
| if (atomic_dec_and_test(&r1_bio->remaining)) {
| - md_done_sync(mddev, r1_bio->master_bio->bi_size >> 9, 0);
| + md_done_sync(mddev, r1_bio->master_bio->bi_size >> 9, 1);
| put_buf(r1_bio);
| }
| }
Has this patch been forwarded to Linus already? It would be nice to
have this fixed before the final 2.6.0 is released.
--
Dick Streefland //// De Bilt
dick.streefland@xs4all.nl (@ @) The Netherlands
------------------------------oOO--(_)--OOo------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
