From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, ed.ciechanowski@intel.com,
marcin.labun@intel.com, dan.j.williams@intel.com
Subject: Re: [PATCH 8/8] Manual update for --continue option
Date: Mon, 3 Oct 2011 10:09:48 +1100 [thread overview]
Message-ID: <20111003100948.1bd85b1c@notabene.brown> (raw)
In-Reply-To: <20110927120539.4890.87894.stgit@gklab-128-013.igk.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]
On Tue, 27 Sep 2011 14:05:39 +0200 Adam Kwolek <adam.kwolek@intel.com> wrote:
> Patch adds to mdadm man the following information:
>
> --continue
> This option is complementary pair to assembly --freeze-reshape option.
> It is needed when --grow operation is interrupted and it is not restarted
> automatically due to --freeze-reshape usage during array assembly.
> Option --continue has to be used together with -G , ( --grow ) command
> and device that it should be executed on. All parameters required for
> reshape continuation will be read from array metadata. If initial
> --grow command had required --backup-file= option to be set,
> continuation option will require to have exactly the same backup
> file pointed to also.
>
> Any other parameter passed together with --continue option will be ignored.
>
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
>
> mdadm.8.in | 27 +++++++++++++++++++++++++++
> 1 files changed, 27 insertions(+), 0 deletions(-)
>
> diff --git a/mdadm.8.in b/mdadm.8.in
> index 3e2f99e..6b0af55 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -734,6 +734,33 @@ The file must be stored on a separate device, not on the RAID array
> being reshaped.
>
> .TP
> +.BR \-\-continue
> +This option is complementary pair to assembly
> +.B \-\-freeze-reshape
> +option. It is needed when
> +.B \-\-grow
> +operation is interrupted and it is not restarted automatically due to
> +.B \-\-freeze-reshape
> +usage during array assembly. Option
> +.BR \-\-continue
> +has to be used together with
> +.BR \-G
> +, (
> +.BR \-\-grow
> +) command and device that it should be executed on.
> +All parameters required for reshape continuation will be read from array metadata.
> +If initial
> +.BR \-\-grow
> +command had required
> +.BR \-\-backup\-file=
> +option to be set, continuation option will require to have exactly the same
> +backup file pointed to also.
> +.IP
> +Any other parameter passed together with
> +.BR \-\-continue
> +option will be ignored.
> +
> +.TP
> .BR \-N ", " \-\-name=
> Set a
> .B name
Thanks.
Both man-page updates added (with some minor fixes).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2011-10-02 23:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 12:04 [PATCH 0/8] Reshape restart after filesystem pivot Adam Kwolek
2011-09-27 12:04 ` [PATCH 1/8] Do not continue reshape during initrd phase Adam Kwolek
2011-10-02 22:19 ` NeilBrown
2011-09-27 12:04 ` [PATCH 2/8] Add continue option to grow command Adam Kwolek
2011-10-02 22:27 ` NeilBrown
2011-09-27 12:04 ` [PATCH 3/8] Do not restart reshape if it is started already Adam Kwolek
2011-10-02 22:41 ` NeilBrown
2011-09-27 12:05 ` [PATCH 4/8] Set correct reshape restart position Adam Kwolek
2011-10-02 22:56 ` NeilBrown
2011-09-27 12:05 ` [PATCH 5/8] Move code to get_data_disks() function Adam Kwolek
2011-10-02 22:58 ` NeilBrown
2011-09-27 12:05 ` [PATCH 6/8] Verify reshape restart position Adam Kwolek
2011-10-02 23:06 ` NeilBrown
2011-09-27 12:05 ` [PATCH 7/8] Manual update for --continue option Adam Kwolek
2011-09-27 12:05 ` [PATCH 8/8] " Adam Kwolek
2011-10-02 23:09 ` 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=20111003100948.1bd85b1c@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=marcin.labun@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).