linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: majianpeng <majianpeng@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk.
Date: Mon, 4 Mar 2013 13:04:35 +1100	[thread overview]
Message-ID: <20130304130435.4113d2a4@notabene.brown> (raw)
In-Reply-To: <201302281550356268273@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]

On Thu, 28 Feb 2013 15:50:37 +0800 majianpeng <majianpeng@gmail.com> wrote:

> Replacement is a fullsync which don't depent on bitmap.So regardless of
> the presence and absence of bitmap, it do full resync.
> If offset of normal io is larger than offset of resync,it will write
> again when resync arrived this offset.

This might be OK for RAID1 and RAID10 as recover is paused when writes
happen, but that is not the case for RAID5, so it isn't safe to test against
curr_resync - it gets updated a bit too later.

Also you messed up the formatting in raid10.c

I'm not convinced this optimisation is really worth it.

NeilBrown


> 
> Signed-off-by: Jianpeng Ma <majianpeng@gmail.com>
> ---
>  drivers/md/raid1.c  |    4 +++-
>  drivers/md/raid10.c |    4 +++-
>  drivers/md/raid5.c  |    3 ++-
>  3 files changed, 8 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
> index d5bddfc..142a5fa 100644
> --- a/drivers/md/raid1.c
> +++ b/drivers/md/raid1.c
> @@ -1173,7 +1173,9 @@ read_again:
>  				set_bit(R1BIO_Degraded, &r1_bio->state);
>  			continue;
>  		}
> -
> +		if (test_bit(Replacement, &rdev->flags) &&
> +			conf->mddev->curr_resync < r1_bio->sector)
> +			continue;
>  		atomic_inc(&rdev->nr_pending);
>  		if (test_bit(WriteErrorSeen, &rdev->flags)) {
>  			sector_t first_bad;
> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
> index 64d4824..bb11cfb 100644
> --- a/drivers/md/raid10.c
> +++ b/drivers/md/raid10.c
> @@ -1337,7 +1337,9 @@ retry_write:
>  			     || test_bit(Unmerged, &rdev->flags)))
>  			rdev = NULL;
>  		if (rrdev && (test_bit(Faulty, &rrdev->flags)
> -			      || test_bit(Unmerged, &rrdev->flags)))
> +			|| test_bit(Unmerged, &rrdev->flags) || 
> +			(test_bit(Replacement, &rrdev->flags) &&
> +			conf->mddev->curr_resync < r10_bio->sector)))
>  			rrdev = NULL;
>  
>  		r10_bio->devs[i].bio = NULL;
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index bd49623..e0a2a39 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -602,7 +602,8 @@ static void ops_run_io(struct stripe_head *sh, struct stripe_head_state *s)
>  			rdev = NULL;
>  		if (rdev)
>  			atomic_inc(&rdev->nr_pending);
> -		if (rrdev && test_bit(Faulty, &rrdev->flags))
> +		if (rrdev && (test_bit(Faulty, &rrdev->flags) ||
> +			conf->mddev->curr_resync < sh->sector))
>  			rrdev = NULL;
>  		if (rrdev)
>  			atomic_inc(&rrdev->nr_pending);


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-03-04  2:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28  7:50 [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk majianpeng
2013-03-04  2:04 ` NeilBrown [this message]
2013-03-04  2:24   ` majianpeng
2013-03-04  5:30     ` NeilBrown
2013-03-05  2:53       ` majianpeng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130304130435.4113d2a4@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=majianpeng@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).