From: Guoqing Jiang <gqjiang@suse.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/2] Check node nums for cluster raid
Date: Wed, 4 May 2016 23:03:11 -0400 [thread overview]
Message-ID: <572AB7EF.6090403@suse.com> (raw)
In-Reply-To: <wrfjinytx3fv.fsf@redhat.com>
Hi Jes,
On 05/04/2016 11:12 AM, Jes Sorensen wrote:
> Guoqing Jiang <gqjiang@suse.com> writes:
>> For cluster raid, we do need at least two nodes for it,
>> the two patches add the checks before create and change
>> bitmap.
>>
>> Thanks,
>> Guoqing
>>
>> Guoqing Jiang (2):
>> Create: check the node nums when create clustered raid
>> super1: don't update node nums if it is not more than 1
>>
>> Create.c | 7 ++++++-
>> super1.c | 5 +++++
>> 2 files changed, 11 insertions(+), 1 deletion(-)
> Hi Guoqing,
>
> I am a little confused on this one - albeit I haven't looked at it in
> detail. Why should it not be possible to start a cluster with one node?
> In theory you should be able to do that, and then add nodes later?
The "nodes" means how many nodes could run with the clustered raid.
IOW, if nodes is set to 1, then we can't assemble the clustered raid in
node B after clustered raid is created in node A.
And we had provided below protection in md-cluster.c, so it doesn't make
sense to create clustered raid with "nodes = 1" since we can't use this raid
across cluster.
f (nodes < cinfo->slot_number) {
pr_err("md-cluster: Slot allotted(%d) is greater than
available slots(%d).",
cinfo->slot_number, nodes);
ret = -ERANGE;
goto err;
}
Regards,
Guoqing
next prev parent reply other threads:[~2016-05-05 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 8:33 [PATCH 0/2] Check node nums for cluster raid Guoqing Jiang
2016-05-04 8:33 ` [PATCH 1/2] Create: check the node nums when create clustered raid Guoqing Jiang
2016-05-04 8:33 ` [PATCH 2/2] super1: don't update node nums if it is not more than 1 Guoqing Jiang
2016-05-04 15:12 ` [PATCH 0/2] Check node nums for cluster raid Jes Sorensen
2016-05-04 15:19 ` Doug Ledford
2016-05-04 15:25 ` Jes Sorensen
2016-05-04 15:28 ` Doug Ledford
2016-05-05 3:03 ` Guoqing Jiang [this message]
2016-05-05 20:28 ` 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=572AB7EF.6090403@suse.com \
--to=gqjiang@suse.com \
--cc=Jes.Sorensen@redhat.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).