[DRBD-user] drbd-0.7.0 left dead, dazed and confused after seeing -preX peer

Andreas Schultz aschultz at tpip.net
Thu Jul 22 13:42:49 CEST 2004

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


Hi,

While upgrading my system, i have encountered a situation where both peers are 
alive and well, but drbd can still not establish a connection without 
removing and reinserting the drbd modules first.
This happend after i rebooted the second system with an older kernel which 
prompted the first system to terminate it's drbd receiver threads.

The log from the first peer:
Jul 22 12:31:03 sdev01 kernel: drbd0: expected HandShake packet, received 
ReportParams...
Jul 22 12:31:03 sdev01 kernel: drbd0: peer probaly runs some incompatible 0.7 
-preX version
Jul 22 12:31:03 sdev01 kernel: drbd0: Discarding network configuration.
Jul 22 12:31:04 sdev01 kernel: drbd1: expected HandShake packet, received 
ReportParams...
Jul 22 12:31:04 sdev01 kernel: drbd1: peer probaly runs some incompatible 0.7 
-preX version
Jul 22 12:31:04 sdev01 kernel: drbd1: Discarding network configuration.
Jul 22 12:31:04 sdev01 kernel: drbd1: worker terminated
Jul 22 12:31:04 sdev01 kernel: drbd1: Connection lost.
Jul 22 12:31:04 sdev01 kernel: drbd1: receiver terminated
Jul 22 12:31:04 sdev01 kernel: drbd2: expected HandShake packet, received 
ReportParams...
Jul 22 12:31:04 sdev01 kernel: drbd2: peer probaly runs some incompatible 0.7 
-preX version
Jul 22 12:31:04 sdev01 kernel: drbd2: Discarding network configuration.
Jul 22 12:31:04 sdev01 kernel: drbd2: worker terminated
Jul 22 12:31:04 sdev01 kernel: drbd2: Connection lost.
Jul 22 12:31:04 sdev01 kernel: drbd2: receiver terminated
Jul 22 12:31:04 sdev01 kernel: drbd0: worker terminated
Jul 22 12:31:04 sdev01 kernel: drbd0: Connection lost.
Jul 22 12:31:04 sdev01 kernel: drbd0: receiver terminated

...  here all receivers are gone and drbd needs to reloaded to start working 
again.

I have to admit that this is a situation that should not happen in production, 
but i would also argue that _nothing_ should leave a drbd peer in a state 
from which it can not recover automaticly.

Regards

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20040722/21448c27/attachment.pgp>


More information about the drbd-user mailing list