[DRBD-user] Interoperability of 8.0.16 and 8.3.6

Iustin Pop iustin at google.com
Tue Dec 22 14:07:30 CET 2009

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Tue, Dec 22, 2009 at 01:12:00PM +0100, Lars Ellenberg wrote:
> On Thu, Dec 17, 2009 at 04:05:28PM +0100, Iustin Pop wrote:
> > Hi,
> > 
> > DRBD 8.0 says proto:86 and 8.3.6 says proto:86-91, so I would expect
> > these two to work nicely together. And this seems to be the case, except
> > when bringing them up in primary/primary mode.
> > 
> > The problems seems to be that after both devices are in primary/primary
> > and connected state, the 8.0.16 node wants to go back to WFBitMapS and
> > remains there, but the 8.3.6 node refuses it due to: "block drbd0:
> > unexpected cstate (Connected) in receive_bitmap". So 8.0.16 remains
> > stuck in WFBitmapS while 8.3.6 thinks it's in Connected.
> > 
> > Is this something that should work and is maybe a bug (drbd or our
> > configuration), or is it not something realistic to expect?
> It is supposed to work, but it is NOT supposed to be run in that
> configuration for longer than absolutely necessary.
> The interoperability is primarily to support rolling upgrades.
> Not to run for extended periods of time.

Indeed, that is the plan. Well, for some values of "extended", but point

> If you have logs for such an incident,
> show them, maybe it is even something else,
> and has not much to do with the differnt versions.

Given that I can reproduce this quite well when combining 8.0+8.3, but
not 8.0+8.0 or 8.3+8.3, I think it's the version diff. Note that this is
DRBD as used by the ganeti software (i.e. direct use of drbdsetup and
not via drbdadmin), but I'll send actual drbdsetup commands on how this
can be reproduced.

In any case, I'll send some logs (but probably after the holidays).

Thanks for your reply!

More information about the drbd-user mailing list