On Thu, Oct 29, 2015 at 06:11:28PM +0100, Veit Wahlich wrote:
>
> My problem is not that I do not know whether there are two primaries
> active, but whether two primaries are still allowed (esp. whether
> "drbdadm --allow-two-primaeries=no" has been successfully executed.
>
> So I was unable to
Hi Roland,
thank you for your reply.
May I suggest to update the documentation accordingly?
Best regards,
// Veit
> Hi,
>
> it is expected behavior, don't worry, everything is fine. The lowest bit
> is used to encode the role (1 == primary, 0 == secondary IIRC).
>
> Regards, rck
On Mon, Nov 02, 2015 at 04:01:00PM +0100, Veit Wahlich wrote:
> Am Montag, den 02.11.2015, 15:53 +0100 schrieb Lars Ellenberg:
> > What's wrong with
> > # drbdsetup XYZ show --show-defaults
>
> That is exactly what I was looking for, thank you!
>
> Just a little more complicated to parse than I
Am Montag, den 02.11.2015, 17:14 +0100 schrieb Lars Ellenberg:
> res=XYZ
> if drbdsetup show $res | grep -q allow-two-primaries; then
> echo "Two primaries are allowed."
> else
> echo "Two primaries are not allowed."
> fi
>
> complicated to parse?
> where?
Well, for safety reasons I
Hi,
I am observing a quite strage behaviour:
The generation identifier UUIDs on my nodes differ although the volumes
are connected and reported in-sync (in fact they are really in-sync, I
ran a verify).
Regarding to https://drbd.linbit.com/users-guide/s-gi.html this should
not happen.
I find
Am Montag, den 02.11.2015, 15:53 +0100 schrieb Lars Ellenberg:
> What's wrong with
> # drbdsetup XYZ show --show-defaults
That is exactly what I was looking for, thank you!
Just a little more complicated to parse than I hoped for, but feasible
without problems.
Regards,
// Veit
On Mon, Nov 02, 2015 at 01:00:03PM +0100, Veit Wahlich wrote:
> Hi,
>
> I am observing a quite strage behaviour:
>
> The generation identifier UUIDs on my nodes differ although the volumes
> are connected and reported in-sync (in fact they are really in-sync, I
> ran a verify).
>
> Regarding to
