All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] howto enable auto-promote
Date: Wed, 20 May 2015 14:48:36 +0200	[thread overview]
Message-ID: <20150520124836.GX1968@rck.sh> (raw)
In-Reply-To: <1529837518.111.1432124741450.JavaMail.open-xchange@ronja.mits.lan>

On Wed, May 20, 2015 at 02:25:41PM +0200, Dietmar Maurer wrote:
> 
> > Auto-promote is enabled. As you can see it failed, and it can only fail
> > if it was enabled... Your problem is the "multiple primaries" thingy.
> > Please tell us which drbdmanage commands you executed. 
> 
> What commands? The idea is that 'auto-promote' works without any commands.
> So I just start the kvm VM on the second node, which tries to open the device.
> 
> So I tried to enable allow-two-primaries somehow. Adding it 
> to /etc/drbd.d/global_common.conf did not help. 

You probably forgot to "drbdadm adjust"...

> Then I tried:
> 
> # drbdadm net-options --allow-two-primaries=yes vm-100-disk-1
> 
> on each node, and it seems to work now.
> 
> So where is the right place to set allow-two-primaries for 
> volumes managed by drbdmanage? 

Passing these "generic drbd options" to drbdmanage is work in progress.
I expect it to be finished for the next release. 

> And why is that disabled by default? 
> 

Oh, because you really really have to know if two primiaries are a good
idea. Allowing multiple primaries is definitely nothing that should be
enabled by default.

Regards, rck

Again: Please no TO/CC, and please ask such questions on drbd-user.

      reply	other threads:[~2015-05-20 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 10:41 [Drbd-dev] howto enable auto-promote Dietmar Maurer
2015-05-20 12:01 ` Roland Kammerer
2015-05-20 12:25   ` Dietmar Maurer
2015-05-20 12:48     ` Roland Kammerer [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=20150520124836.GX1968@rck.sh \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-dev@lists.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 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.