Hi,
I start fresh in the meantime and everything works fine now. The only
difference is that I added a third node without storage like in this post:
http://lists.linbit.com/pipermail/drbd-user/2017-March/023094.html
Thanks,
Daniel
On Tue, Nov 6, 2018 at 1:28 PM, Lars Ellenberg
wrote:
>
>
Note, just adding "--force" if DRBD refuses to promote
is usually a Very Bad Idea™.
Because usually DRBD has a good reason to refuse promotion.
And "forcing" the role change
does NOT magically make the accessible data any better.
On Fri, Nov 02, 2018 at 09:29:08PM +0200, Daniel Hertanu wrote:
>
Hello Yannis,
I tried that, same result, won't switch to primary.
Daniel
On Fri, Nov 2, 2018 at 9:14 PM, Yannis Milios
wrote:
> Try adding --force parameter in drbdadm command.
>
>
>
> On Friday, November 2, 2018, Daniel Hertanu wrote:
>
>> Hi,
>>
>> I'm running two nodes with DRBD 9 and I
Try adding --force parameter in drbdadm command.
On Friday, November 2, 2018, Daniel Hertanu wrote:
> Hi,
>
> I'm running two nodes with DRBD 9 and I want to simulate a primary node
> crash followed by restoring the access to the data on the secondary node
> left.
>
> So, having the sync done
Hi,
I'm running two nodes with DRBD 9 and I want to simulate a primary node
crash followed by restoring the access to the data on the secondary node
left.
So, having the sync done between the hosts I'm disconnecting the network to
the primary to simulate the crash.
All my attempts to promote the
