On 8/17/07, Mike Accetta <[EMAIL PROTECTED]> wrote:
>
> Neil Brown writes:
> > On Wednesday August 15, [EMAIL PROTECTED] wrote:
> > > Neil Brown writes:
> > > > On Wednesday August 15, [EMAIL PROTECTED] wrote:
> > > > >
> > > ...
> > > This happens in our old friend sync_request_write()? I'm dealing with
> >
> > Yes, that would be the place.
> >
> > > ...
> > > This fragment
> > >
> > > if (j < 0 || test_bit(MD_RECOVERY_CHECK, &mddev->recovery)) {
> > > sbio->bi_end_io = NULL;
> > > rdev_dec_pending(conf->mirrors[i].rdev, mddev);
> > > } else {
> > > /* fixup the bio for reuse */
> > > ...
> > > }
> > >
> > > looks suspicously like any correction attempt for 'check' is being
> > > short-circuited to me, regardless of whether or not there was a read
> > > error. Actually, even if the rewrite was not being short-circuited,
> > > I still don't see the path that would update 'corrected_errors' in this
> > > case. There are only two raid1.c sites that touch 'corrected_errors', one
> > > is in fix_read_errors() and the other is later in sync_request_write().
> > > With my limited understanding of how this all works, neither of these
> > > paths would seem to apply here.
> >
> > hmmm.... yes....
> > I guess I was thinking of the RAID5 code rather than the RAID1 code.
> > It doesn't do the right thing does it?
> > Maybe this patch is what we need. I think it is right.
> >
> > Thanks,
> > NeilBrown
> >
> >
> > Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
> >
> > ### Diffstat output
> > ./drivers/md/raid1.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff .prev/drivers/md/raid1.c ./drivers/md/raid1.c
> > --- .prev/drivers/md/raid1.c 2007-08-16 10:29:58.000000000 +1000
> > +++ ./drivers/md/raid1.c 2007-08-17 12:07:35.000000000 +1000
> > @@ -1260,7 +1260,8 @@ static void sync_request_write(mddev_t *
> > j = 0;
> > if (j >= 0)
> > mddev->resync_mismatches +=
> > r1_bio->sec
> > tors;
> > - if (j < 0 || test_bit(MD_RECOVERY_CHECK,
> > &mddev
> > ->recovery)) {
> > + if (j < 0 || (test_bit(MD_RECOVERY_CHECK,
> > &mdde
> > v->recovery)
> > + && text_bit(BIO_UPTODATE,
> > &sbio->
> > bi_flags))) {
> > sbio->bi_end_io = NULL;
> >
> > rdev_dec_pending(conf->mirrors[i].rdev,
> > mddev);
> > } else {
>
> I tried this (with the typo fixed) and it indeed issues a re-write.
> However, it doesn't seem to do anything with the corrected errors
> count if the rewrite succeeds. Since end_sync_write() is only used one
> other place when !In_sync, I tried the following and it seems to work
> to get the error count updated. I don't know whether this belongs in
> end_sync_write() but I'd think it needs to come after the write actually
> succeeds so that seems like the earliest it could be done.
Neil,
Any feedback on Mike's patch?
thanks,
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
