linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Czarnowska, Anna" <anna.czarnowska@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	"Grabowski, Grzegorz" <grzegorz.grabowski@intel.com>
Subject: Re: [PATCH] Reset bad flag on map update
Date: Thu, 8 Mar 2012 09:26:30 +1100	[thread overview]
Message-ID: <20120308092630.6c992e26@notabene.brown> (raw)
In-Reply-To: <3F8F31A3BFD1664EAB894D1BD6AF32B915714B17@IRSMSX102.ger.corp.intel.com>

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

On Wed, 7 Mar 2012 12:51:30 +0000 "Czarnowska, Anna"
<anna.czarnowska@intel.com> wrote:

> Map file may miss an entry if bad flag is not cleared on update.
> 
> This happens for example when an old entry exists in map that
> has no mdstat counterpart and we create a new array with the same devnum.
> Newly created array will not appear in map if update doesnt clear bad flag.
> 
> Signed-off-by: Anna Czarnowska <anna.czarnowska@intel.com>
> ---
>  mapfile.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/mapfile.c b/mapfile.c
> index 0bfecd0..9e2c893 100644
> --- a/mapfile.c
> +++ b/mapfile.c
> @@ -246,6 +246,7 @@ int map_update(struct map_ent **mpp, int devnum, char *metadata,
>  			memcpy(mp->uuid, uuid, 16);
>  			free(mp->path);
>  			mp->path = path ? strdup(path) : NULL;
> +			mp->bad = 0;
>  			break;
>  		}
>  	if (!mp)

applied, thanks.

NeilBrown

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

      reply	other threads:[~2012-03-07 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 12:51 [PATCH] Reset bad flag on map update Czarnowska, Anna
2012-03-07 22:26 ` 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=20120308092630.6c992e26@notabene.brown \
    --to=neilb@suse.de \
    --cc=anna.czarnowska@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=grzegorz.grabowski@intel.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).