From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: zhilong <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Add '--nodes' option in GROW mode
Date: Tue, 22 Mar 2016 13:56:38 -0400 [thread overview]
Message-ID: <wrfjshzi9z1l.fsf@redhat.com> (raw)
In-Reply-To: <56F13020.8020900@suse.com> (zhilong's message of "Tue, 22 Mar 2016 19:44:32 +0800")
zhilong <zlliu@suse.com> writes:
> Bug description:
> # mdadm -Cv /dev/md0 --bitmap=clustered -l1 -n2 /dev/sdd /dev/sdb
> --nodes=6 --assume-clean
> # mdadm --grow /dev/md0 --bitmap=none
> # mdadm --grow /dev/md0 --bitmap=clustered
> -> cluster nodes would be changed to 4, here is my method to
> resolve it.
> # mdadm --grow /dev/md0 --bitmap=clustered --nodes=6
>
> Patch:
>
> Cluster nodes is set 4 as default when switch bitmap from
> none to clustered under GROW mode, so add '--nodes'
> option in GROW mode.
>
> Signed-off-by: Zhilong Liu <zlliu@suse.com>
> ---
> mdadm.c | 1 +
> 1 file changed, 1 insertion(+)
Hi,
I have a question about this, since I simply do not have the knowledge
about clustering to judge this approach.
If you remove the bitmap, does that 'uncluster' the array? If not,
shouldn't mdadm be fixed to not set #nodes to 4 when adding a clustered
bitmap, if a number of cluster nodes is already present?
Thanks,
Jes
>
> diff --git a/mdadm.c b/mdadm.c
> index 51e16f3..b542b8c 100644
> --- a/mdadm.c
> +++ b/mdadm.c
> @@ -592,6 +592,7 @@ int main(int argc, char *argv[])
> ident.raid_disks = s.raiddisks;
> continue;
> case O(ASSEMBLE, Nodes):
> + case O(GROW, Nodes):
> case O(CREATE, Nodes):
> c.nodes = parse_num(optarg);
> if (c.nodes <= 0) {
next prev parent reply other threads:[~2016-03-22 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 11:44 [PATCH] Add '--nodes' option in GROW mode zhilong
2016-03-22 17:56 ` Jes Sorensen [this message]
2016-03-23 11:38 ` Guoqing Jiang
2016-03-24 16:31 ` Jes Sorensen
2016-03-25 2:22 ` [PATCH] mdadm:Add " zhilong
2016-03-29 15:43 ` Jes Sorensen
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=wrfjshzi9z1l.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=zlliu@suse.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.