linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Lukasz Dorau <lukasz.dorau@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
	marcin.labun@intel.com, ed.ciechanowski@intel.com
Subject: Re: [PATCH] fix: correct metadata's update communication
Date: Mon, 21 Nov 2011 16:19:56 +1100	[thread overview]
Message-ID: <20111121161956.06352812@notabene.brown> (raw)
In-Reply-To: <20111118143433.14114.6361.stgit@gklab-128-085.igk.intel.com>

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

On Fri, 18 Nov 2011 15:34:33 +0100 Lukasz Dorau <lukasz.dorau@intel.com>
wrote:

> The problem occurs when array under migration is assembled incrementally.
> st->update_tail is not initialized in function
> assemble_container_content() and during reshape
> the checkpoint information in metadata is not being updated.
> 
> The value of st->update_tail is now initialized in function
> assemble_container_content() and during reshape the checkpoint
> information in metadata is being updated correctly on all disks.
> 
> Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com>
> ---
>  Assemble.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/Assemble.c b/Assemble.c
> index 3c8e74d..74708d1 100644
> --- a/Assemble.c
> +++ b/Assemble.c
> @@ -1585,6 +1585,9 @@ int assemble_container_content(struct supertype *st, int mdfd,
>  				if (!mdmon_running(st->container_dev))
>  					start_mdmon(st->container_dev);
>  				ping_monitor_by_id(st->container_dev);
> +				if (mdmon_running(st->container_dev) &&
> +						st->update_tail == NULL)
> +					st->update_tail = &st->updates;
>  			}
>  
>  			err = Grow_continue(mdfd, st, content, backup_file,


This and the previous patch ( [PATCH] imsm: fix: correct printing value of
blocks per migration unit) applied - thanks.

NeilBrown


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

      reply	other threads:[~2011-11-21  5:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 14:34 [PATCH] fix: correct metadata's update communication Lukasz Dorau
2011-11-21  5:19 ` 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=20111121161956.06352812@notabene.brown \
    --to=neilb@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.dorau@intel.com \
    --cc=marcin.labun@intel.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).