linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Alexander Lyakas <alex.bolshoy@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: mdadm: [PATCH] Don't consider disks with a valid recovery offset as candidates for bumping up event count
Date: Tue, 15 May 2012 14:21:04 +1000	[thread overview]
Message-ID: <20120515142104.41a80d73@notabene.brown> (raw)
In-Reply-To: <CAGRgLy5tEups--dzoV6+bq+CzZzwYMy7tv0FFJqah-Q5ZJc6kA@mail.gmail.com>

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

On Sun, 13 May 2012 13:10:43 +0300 Alexander Lyakas <alex.bolshoy@gmail.com>
wrote:

> Hi Neil,
> do you think the below patch sounds reasonable?

Yes, looks good.  Applied.

Thanks,
NeilBrown



> 
> Thanks,
> Alex.
> 
> 
> >From 98adc21bba9cf5d77214d665f2218fd7de2623b9 Mon Sep 17 00:00:00 2001
> From: Alex Lyakas <alex@zadarastorage.com>
> Date: Sun, 13 May 2012 13:04:24 +0300
> Subject: [PATCH] Don't consider disks with a valid recovery offset as
>  candidates for bumping up event count.
> 
> When we are looking for a candidate disk to bump up the event count,
> we consider only disks that have recovery_start==MaxSector.
> However, after we find one such disk, we agree to accept more disks
> having same event count, regardless of their recovery_start.
> Be consistent and don't accept disks with a valid recovery_start at all.
> 
> diff --git a/Assemble.c b/Assemble.c
> index 080993d..227d66f 100644
> --- a/Assemble.c
> +++ b/Assemble.c
> @@ -1069,6 +1069,7 @@ int Assemble(struct supertype *st, char *mddev,
>                         int j = best[i];
>                         if (j >= 0 &&
>                             !devices[j].uptodate &&
> +                           devices[j].i.recovery_start == MaxSector &&
>                             devices[j].i.events == current_events) {
>                                 chosen_drive = j;
>                                 goto add_another;
> --
> 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


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

      reply	other threads:[~2012-05-15  4:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 10:10 mdadm: [PATCH] Don't consider disks with a valid recovery offset as candidates for bumping up event count Alexander Lyakas
2012-05-15  4:21 ` NeilBrown [this message]

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=20120515142104.41a80d73@notabene.brown \
    --to=neilb@suse.de \
    --cc=alex.bolshoy@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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).