[DRBD-user] Weird protocol errors

Igmar Palsenberg igmar at palsenberg.com
Wed Jun 29 14:39:54 CEST 2011

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



> Somehow by 2 machine drbd setup got screwed (seriously) : 
> 
> Jun 29 01:51:48 jdi kernel: block drbd0: Handshake successful: Agreed network protocol version 95
> Jun 29 01:51:48 jdi kernel: block drbd0: conn( WFConnection -> WFReportParams )
> Jun 29 01:51:48 jdi kernel: block drbd0: Starting asender thread (from drbd0_receiver [7914])
> Jun 29 01:51:48 jdi kernel: block drbd0: unknown packet type 16, l: 64!
> Jun 29 01:51:48 jdi kernel: block drbd0: conn( WFReportParams -> ProtocolError ) 
> Jun 29 01:51:48 jdi kernel: block drbd0: asender terminated
> Jun 29 01:51:48 jdi kernel: block drbd0: Terminating asender thread
> Jun 29 01:51:48 jdi kernel: block drbd0: Connection closed
> Jun 29 01:51:48 jdi kernel: block drbd0: conn( ProtocolError -> Unconnected )
> Jun 29 01:51:48 jdi kernel: block drbd0: receiver terminated
> Jun 29 01:51:48 jdi kernel: block drbd0: Restarting receiver thread
> Jun 29 01:51:48 jdi kernel: block drbd0: receiver (re)started
> Jun 29 01:51:48 jdi kernel: block drbd0: conn( Unconnected -> WFConnection )
> 
> 
> Notice the 'unknown packet type' stuff. Anyone got a clue ? This is 8.3.10 talking to 8.3.9. The same issue with 8.3.9 <--> 8.3.9
> I'm kinda list here, anyone got some good advise ?

Found it. The installer bluntly overwrote my global config, instead of only overwriting the kernel drbd.ko. That results in a mismatch on parameters, including authentication and protocol. Making those in sync again will probably make things work again.


Regards,


	Igmar


More information about the drbd-user mailing list