From: NeilBrown <neilb@suse.de>
To: Krzysztof Wojcik <krzysztof.wojcik@intel.com>
Cc: linux-raid@vger.kernel.org, wojciech.neubauer@intel.com,
adam.kwolek@intel.com, dan.j.williams@intel.com,
ed.ciechanowski@intel.com
Subject: Re: [PATCH 00/22] IMSM checkpointing implementation
Date: Wed, 8 Jun 2011 17:23:49 +1000 [thread overview]
Message-ID: <20110608172349.5ee242c9@notabene.brown> (raw)
In-Reply-To: <20110602144212.27355.3706.stgit@gklab-128-111.igk.intel.com>
On Thu, 02 Jun 2011 16:48:08 +0200 Krzysztof Wojcik
<krzysztof.wojcik@intel.com> wrote:
> IMSM for securing reshape process uses special disk area outside metadata
> for reshaped area backup purposes. If just reshaped array area requires
> backup, bunch of array stripes prepared for reshape is stored in to
> Migration Copy Area. In case of reshape interruption, Option ROM during
> restart or mdadm during reshape restart (when no reboot occurs) will
> restore Migration Copy Area to designation array.
> Reshape can be continued form stable array stable state.
>
> The following series implements IMSM checkpointing procedure.
I have applied most of these patches - some with some minor fixes. The major
changes I have already mentioned.
I will wait for you responses to those changes, and the other bug fixes you
mentioned before considering a release of 3.2.2, but I would like to make
that release in the next week or two.
Thanks,
NeilBrown
>
> ---
>
> Adam Kwolek, Krzysztof Wojcik (22):
> imsm: Add migration record to intel_super
> Support restore_stripes() from the given buffer
> Define dummy functions to mdmon.c
> imsm: Add support for copy area and backup operations
> imsm: check migration compatibility
> FIX: Initialize reshape structure
> imsm: Add wait_for_reshape_imsm() implementation
> imsm: Implement imsm_manage_reshape(), reshape workhorse
> imsm: Check if array degradation has been changed
> imsm: Clear migration record when no migration in progress
> imsm: Add information about migration record to mdadm '-E' option
> imsm: update blocks_per_migr_unit() to support migration record
> Add reshape restart support for external metadata
> imsm: Implement recover_backup_imsm() for imsm metadata
> imsm: Disable checkpoint updating by mdmon for general migration
> imsm: Add metadata update type for general migration check-pointing
> imsm: Prepare checkpoint update for general migration
> imsm: Apply checkpoint metadata update for general migration
> FIX: Enable metadata updates for raid0
> Do not use backup file for external metadata
> imsm: Remove user warning before reshape start
> imsm: Unit Tests - remove backup-file during grow command
>
>
> Assemble.c | 10
> Grow.c | 50 +-
> mdadm.h | 7
> mdmon.c | 23 +
> restripe.c | 101 +++-
> super-intel.c | 1241 ++++++++++++++++++++++++++++++++++++++++++++--
> tests/imsm-grow-template | 5
> 7 files changed, 1322 insertions(+), 115 deletions(-)
>
next prev parent reply other threads:[~2011-06-08 7:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 14:48 [PATCH 00/22] IMSM checkpointing implementation Krzysztof Wojcik
2011-06-02 14:48 ` [PATCH 01/22] imsm: Add migration record to intel_super Krzysztof Wojcik
2011-06-02 14:48 ` [PATCH 02/22] Support restore_stripes() from the given buffer Krzysztof Wojcik
2011-06-02 14:48 ` [PATCH 03/22] Define dummy functions to mdmon.c Krzysztof Wojcik
2011-06-02 14:48 ` [PATCH 04/22] imsm: Add support for copy area and backup operations Krzysztof Wojcik
2011-06-02 14:48 ` [PATCH 05/22] imsm: check migration compatibility Krzysztof Wojcik
2011-06-02 14:49 ` [PATCH 06/22] FIX: Initialize reshape structure Krzysztof Wojcik
2011-06-08 6:54 ` NeilBrown
2011-06-02 14:49 ` [PATCH 07/22] imsm: Add wait_for_reshape_imsm() implementation Krzysztof Wojcik
2011-06-08 7:07 ` NeilBrown
2011-06-02 14:49 ` [PATCH 08/22] imsm: Implement imsm_manage_reshape(), reshape workhorse Krzysztof Wojcik
2011-06-02 14:49 ` [PATCH 09/22] imsm: Check if array degradation has been changed Krzysztof Wojcik
2011-06-02 14:49 ` [PATCH 10/22] imsm: Clear migration record when no migration in progress Krzysztof Wojcik
2011-06-02 14:49 ` [PATCH 11/22] imsm: Add information about migration record to mdadm '-E' option Krzysztof Wojcik
2011-06-02 14:49 ` [PATCH 12/22] imsm: update blocks_per_migr_unit() to support migration record Krzysztof Wojcik
2011-06-02 14:49 ` [PATCH 13/22] Add reshape restart support for external metadata Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 14/22] imsm: Implement recover_backup_imsm() for imsm metadata Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 15/22] imsm: Disable checkpoint updating by mdmon for general migration Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 16/22] imsm: Add metadata update type for general migration check-pointing Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 17/22] imsm: Prepare checkpoint update for general migration Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 18/22] imsm: Apply checkpoint metadata " Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 19/22] FIX: Enable metadata updates for raid0 Krzysztof Wojcik
2011-06-02 14:50 ` [PATCH 20/22] Do not use backup file for external metadata Krzysztof Wojcik
2011-06-02 14:51 ` [PATCH 21/22] imsm: Remove user warning before reshape start Krzysztof Wojcik
2011-06-02 14:51 ` [PATCH 22/22] imsm: Unit Tests - remove backup-file during grow command Krzysztof Wojcik
2011-06-08 7:23 ` NeilBrown [this message]
2011-06-08 7:34 ` [PATCH 00/22] IMSM checkpointing implementation Wojcik, Krzysztof
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=20110608172349.5ee242c9@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=krzysztof.wojcik@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).