All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Lukasz Orlowski <lukasz.orlowski@intel.com>
Cc: dan.j.williams@intel.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10
Date: Sat, 22 Oct 2011 11:50:19 +1100	[thread overview]
Message-ID: <20111022115019.1aa1fc78@notabene.brown> (raw)
In-Reply-To: <20111021074643.14969.22068.stgit@gklab-128-192.igk.intel.com>

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

On Fri, 21 Oct 2011 09:47:29 +0200 Lukasz Orlowski
<lukasz.orlowski@intel.com> wrote:

> The following series fixes metadata updates handling code after migration from Raid 0 to Raid 10:
> Last disk is left as a spare instead of being activated and a missing disk is a
> member of an array instead of being removed. The array status is degraded
> instead of normal.
> 
> ---
> 
> Lukasz Orlowski (1):
>       imsm: Moves metadata update code for spare activation to separate function
> 
> Lukasz Orlowski (1):
>       imsm: fix: Fixes metadata after migration from Raid 0 to Raid 10
> 
> 
>  super-intel.c |  207 +++++++++++++++++++++++++++++++--------------------------
>  1 files changed, 114 insertions(+), 93 deletions(-)
> 

Thanks.
I've applied this with some re-indenting (which suspect you only left that
way to it was easier to see exactly where the changes were).

Thanks,
NeilBrown

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

      parent reply	other threads:[~2011-10-22  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21  7:47 [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10 Lukasz Orlowski
2011-10-21  7:47 ` [PATCH 1/2] imsm: Moves metadata update code for spare activation to separate function Lukasz Orlowski
2011-10-21  7:47 ` [PATCH 2/2] imsm: fix: Fixes metadata after migration from Raid 0 to Raid 10 Lukasz Orlowski
2011-10-22  0:50 ` 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=20111022115019.1aa1fc78@notabene.brown \
    --to=neilb@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.orlowski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.