linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/2] man mdadm: Add note about auto-assembly during array reshape
Date: Wed, 23 Mar 2011 12:04:23 +1100	[thread overview]
Message-ID: <20110323120423.1be12cc2@notabene.brown> (raw)
In-Reply-To: <20110322114643.30235.53813.stgit@gklab-128-013.igk.intel.com>

On Tue, 22 Mar 2011 12:46:43 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:

> Add note to man that auto-assembly cannot be used for reshaped arrays.
> 
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
> 
>  mdadm.8.in |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/mdadm.8.in b/mdadm.8.in
> index 96945ae..2285d4f 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -1665,6 +1665,12 @@ The reason for requiring arrays to be tagged with the homehost for
>  auto assembly is to guard against problems that can arise when moving
>  devices from one host to another.
>  ..
> +Note: Auto assembly cannot be used for assembling and activating arrays
> +under reshape.
> +.B Scan
> +doesn't allow for
> +.B backup\-file
> +passing, required by reshape restart and continuation.
>  
>  .SH BUILD MODE
>  

Applied with some revisions - thanks.

NeilBrown

commit 246cebdb7601fc41ee0cca9a5379cdd7dc072380
Author: Adam Kwolek <adam.kwolek@intel.com>
Date:   Wed Mar 23 12:02:28 2011 +1100

    man mdadm: Add note about auto-assembly during array reshape
    
    Add note to man that auto-assembly cannot be used for reshaped arrays.
    
    Revisions: NeilBrown
    
    Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
    Signed-off-by: NeilBrown <neilb@suse.de>

diff --git a/mdadm.8.in b/mdadm.8.in
index 9537304..982991d 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -1665,6 +1665,13 @@ The reason for requiring arrays to be tagged with the homehost for
 auto assembly is to guard against problems that can arise when moving
 devices from one host to another.
 ..
+Note: Auto assembly cannot be used for assembling and activating some
+arrays which are undergoing reshape.  In particular as the
+.B backup\-file
+cannot be given, any reshape which requires a backup-file to continue
+cannot be started by auto assembly.  An array which is growing to more
+devices and has passed the critical section can be assembled using
+auto-assembly.
 
 .SH BUILD MODE
 

  reply	other threads:[~2011-03-23  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 11:46 [PATCH 1/2] man mdadm: add information for MDADM_EXPERIMENTAL flag Adam Kwolek
2011-03-22 11:46 ` [PATCH 2/2] man mdadm: Add note about auto-assembly during array reshape Adam Kwolek
2011-03-23  1:04   ` NeilBrown [this message]
2011-03-22 13:10 ` [PATCH 1/2] man mdadm: add information for MDADM_EXPERIMENTAL flag Mathias Burén
2011-03-23  1:03   ` NeilBrown

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=20110323120423.1be12cc2@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).