linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Labun, Marcin" <Marcin.Labun@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"Neubauer, Wojciech" <Wojciech.Neubauer@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	"Williams, Dan J" <dan.j.williams@intel.com>
Subject: Re: [PATCH 2/2] 11spare-migration: pass conditions for tests 9 and 12 should be reversed
Date: Mon, 31 Jan 2011 11:36:46 +1100	[thread overview]
Message-ID: <20110131113646.4bbbf0f4@notabene.brown> (raw)
In-Reply-To: <905EDD02F158D948B186911EB64DB3D17701BDF1@irsmsx503.ger.corp.intel.com>

On Fri, 28 Jan 2011 16:48:33 +0000 "Labun, Marcin" <Marcin.Labun@intel.com>
wrote:

> >From a134fc58a6af107a05304a574ad6346cba3fff46 Mon Sep 17 00:00:00 2001
> From: Marcin Labun <marcin.labun@intel.com>
> Date: Thu, 27 Jan 2011 16:19:45 +0100
> Subject: [PATCH 2/2] 11spare-migration: pass conditions for tests 9 and 12 should be reversed
> 
> Test 9: We do not block spare migration between different metadatas.
> test 13: Migrated spare must belong the same domain as destination -
> there is no additional condition for action.
> 
> Signed-off-by: Marcin Labun <marcin.labun@intel.com>
> ---
>  tests/11spare-migration |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/11spare-migration b/tests/11spare-migration
> index 02d19fa..01693e4 100644
> --- a/tests/11spare-migration
> +++ b/tests/11spare-migration
> @@ -232,7 +232,7 @@ tidyup
>  
>  test9()
>  {
> -dsc "Test 9: imsm and native 1.2 - spare should not be shared"
> +dsc "Test 9: imsm and native 1.2 - spare should be shared"
>  setupdevs 0 10 11 imsm
>  setupdevs 1 8 9 1.2
>  createconfig a
> @@ -240,7 +240,7 @@ createconfig domain0 noplatform spare 8 9 10 11 12
>  monitor 0 1
>  mdadm -a /dev/$c1 $dev12
>  mdadm --fail /dev/$v0 $dev10
> -chksparemoved $c1 $c0 $dev12 n
> +chksparemoved $c1 $c0 $dev12
>  tidyup
>  }
>  
> @@ -303,7 +303,7 @@ tidyup
>  
>  test13()
>  {
> -dsc "Test 13: Common domain, two containers, fail a disk in container, action is below spare, the spare should not be moved"
> +dsc "Test 13: Common domain, two containers, fail a disk in container, action is below spare, the spare should be moved regadless of action"
>  setupdevs 0 0 1 $platform
>  setupdevs 1 4 5 $platform
>  # same domain but different action on 4 5 6
> @@ -313,7 +313,7 @@ createconfig domain-$platform $platform include 4 5 6
>  monitor 0 1
>  mdadm -a /dev/$c1 $dev6
>  mdadm --fail /dev/$v0 $dev0
> -chksparemoved $c1 $c0 $d6 n
> +chksparemoved $c1 $c0 $d6
>  tidyup
>  }
>  


Applied, thanks.

NeilBrown


      reply	other threads:[~2011-01-31  0:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 16:48 [PATCH 2/2] 11spare-migration: pass conditions for tests 9 and 12 should be reversed Labun, Marcin
2011-01-31  0:36 ` 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=20110131113646.4bbbf0f4@notabene.brown \
    --to=neilb@suse.de \
    --cc=Marcin.Labun@intel.com \
    --cc=Wojciech.Neubauer@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@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).