From: "Nick Wang" <nwang@suse.com>
To: "Lars Ellenberg" <lars.ellenberg@linbit.com>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH] drbd-utils: Fix the default node id initialization when upgrade v8 to v9
Date: Sun, 15 Jan 2017 19:30:39 -0700 [thread overview]
Message-ID: <587CA0CF02000070000ABE6F@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20170113110345.GA9172@soda.linbit>
>>> On 2017-1-13 at 19:03, in message <20170113110345.GA9172@soda.linbit>, Lars
Ellenberg <lars.ellenberg@linbit.com> wrote:
> With DRBD 9, you *have* to set the node id in the configuration.
> If there is a way around that, we need to fix it.
>
I can see error messages when lacking of node-id or connection sections in multiple nodes scenario.
> Also, IMO, in virtually all 8 -> 9 upgrade scenarios, you are better off
> creating new DRBD 9 meta data instead of trying to "convert".
>
Thanks for the information. Will always do so when upgrading from v8 to v9.
Best regards,
Nick
next prev parent reply other threads:[~2017-01-16 2:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 6:15 [Drbd-dev] [PATCH] drbd-utils: Fix the default node id initialization when upgrade v8 to v9 Nick Wang
2017-01-13 9:00 ` Roland Kammerer
2017-01-13 11:03 ` Lars Ellenberg
2017-01-16 2:30 ` Nick Wang [this message]
[not found] ` <F749D893-B652-4BA8-AA15-AD88344EE2F9@acsalaska.com>
2017-01-16 10:35 ` Lars Ellenberg
2017-01-18 3:14 ` Nick Wang
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=587CA0CF02000070000ABE6F@prv-mh.provo.novell.com \
--to=nwang@suse.com \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.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