Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Dec 08, 2010 at 12:37:07PM +1100, Tim Sharpe wrote: > Hi all, > > I was upgrading one of our older DRBD pairs from 8.3.2 to 8.3.7 today > and ran into a bit of a problem. I took the resources on the > secondary down, upgraded the kernel & DRBD, rebooted and brought the > resources back up again. One of the resources on the secondary > refused to reconnect to the primary server however the other 15 > connected and resynced fine. > > Here's the log for the resource > block drbd12: drbd_sync_handshake: > block drbd12: self 113BE4C4974DBB16:0000000000000000:FDD46B6FD6F2C788:80EFD64D4EC7ECC7 bits:0 flags:0 > block drbd12: peer 113BE4C4974DBB17:FDD46B6FD6F2C789:80EFD64D4EC7ECC7:F88BD898114DD15D bits:4842 flags:0 > block drbd12: uuid_compare()=-1001 by rule 30 > block drbd12: To resolve this both sides have to support at least protocol That should read "at least protocol 91", which according to changelog is DRBD version >= 8.3.3. > It looks like it's handshaking and agreeing on a common protocol fine, > but then disconnects with a message to the contrary. Has anyone run > into a similar situation? So as soon as you have upgraded on both sides, drbd should be able to resolve that. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed