From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
ed.ciechanowski@intel.com, wojciech.neubauer@intel.com
Subject: Re: [PATCH 0/7] Grow_continue, use in assembly (cont.)
Date: Wed, 2 Mar 2011 12:30:32 +1100 [thread overview]
Message-ID: <20110302123032.6d1996ca@notabene.brown> (raw)
In-Reply-To: <20110301144932.10678.20916.stgit@gklab-128-013.igk.intel.com>
On Tue, 01 Mar 2011 15:56:41 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> The following series implements next part of resuming reshape from checkpoint.
> In this series call to invoke reshape is included.
> It is required to have backup file to run reshape, so backup file validation is added
> (without checking in file system)
> Array seams to be configured for reshape, monitor is blocked and doesn't makes changes
> to process. On the end of reshape monitor unblock is placed also.
>
> In patch:
> Continue reshape after assembling array
> some plans for supporting container operations is placed.
>
> Reshape restoring is not working yet (a few more pathes are still required)
> I hope some of therm I'll post tomorrow.
>
> BR
> Adam
>
> ---
>
> Adam Kwolek (7):
> FIX: array is frozen after reshape
> Continue reshape after assembling array
> FIX: Block monitor when starting array with reshape in progress
> Add block_subarray()
> FIX: configure disks slot for expansion
> FIX: reshape in md should wait for monitoring process (external metadata)
> FIX: Verify Backup file name before reshape
>
>
> Assemble.c | 64 +++++++++++++++++++++++++++++++++++++++++++++------------
> Grow.c | 15 ++++++++++++-
> Incremental.c | 1 +
> msg.c | 18 ++++++++++++----
> msg.h | 2 ++
> 5 files changed, 81 insertions(+), 19 deletions(-)
>
I have applied the patches among these which make sense, and replied to the
ones that really don't.
If you think one of the patches that I rejected really is needed, please
provide specific detail of what you try to do, how it doesn't work, and what
you think is the reason.
All applied patches have been pushed to my devel-3.2 branch.
Thanks,
NeilBrown
next prev parent reply other threads:[~2011-03-02 1:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 14:56 [PATCH 0/7] Grow_continue, use in assembly (cont.) Adam Kwolek
2011-03-01 14:56 ` [PATCH 1/7] FIX: Verify Backup file name before reshape Adam Kwolek
2011-03-02 1:01 ` NeilBrown
2011-03-02 7:39 ` Kwolek, Adam
2011-03-01 14:56 ` [PATCH 2/7] FIX: reshape in md should wait for monitoring process (external metadata) Adam Kwolek
2011-03-02 1:06 ` NeilBrown
2011-03-01 14:57 ` [PATCH 3/7] FIX: configure disks slot for expansion Adam Kwolek
2011-03-02 1:10 ` NeilBrown
2011-03-02 7:48 ` Kwolek, Adam
2011-03-01 14:57 ` [PATCH 4/7] Add block_subarray() Adam Kwolek
2011-03-01 14:57 ` [PATCH 5/7] FIX: Block monitor when starting array with reshape in progress Adam Kwolek
2011-03-01 14:57 ` [PATCH 6/7] Continue reshape after assembling array Adam Kwolek
2011-03-01 14:57 ` [PATCH 7/7] FIX: array is frozen after reshape Adam Kwolek
2011-03-02 1:30 ` NeilBrown [this message]
2011-03-02 7:49 ` [PATCH 0/7] Grow_continue, use in assembly (cont.) Kwolek, Adam
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=20110302123032.6d1996ca@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=wojciech.neubauer@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).