Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2004-07-07 21:41:37 -0400 \ Jeff Tucker: > --On Wednesday, July 07, 2004 4:32 PM +0200 Lars Ellenberg > <Lars.Ellenberg at linbit.com> wrote: > > > > >please try again with current cvs, > >these errors are likely to be related. > > > > So I tried again. I compiled the latest CVS against a 2.6.7 kernel and > rebooted the secondary computer. > > First, I see that CVS has gone back to the -pre8 version number. I'm sure I > have the latest CVS since I had files with changes dated today, including > that bitmap stuff and changes to bash and perl scripts. That's not a big > deal, I guess. somehow I got the impression that the -pre9 tag never reached cvs ?? anyways, updated to -pre10... > Second, the secondary wouldn't connect to the primary and had lots of error > messages. I rebooted using 2.6.6 and my older (the first -pre8) DRBD and it > connected fine. > > Here are the errors I got trying to use the CVS version on the secondary: > I got errors like this on the primary as well. > > Is it possible this is because I was running -pre8 on the primary and the > new CVS on the secondary? Do those have to be upgraded simultaneously? while fixing some 32<->64 bit issues, we had to allign all our packets to 64bit, to make them on-the-wire compatible. the first ever exchanged packet (parameter exchange handshake) changed its size, and the code in there could not cope with that. we definetely need to introduce a new "fixed-size-for-the-next-100-years" handshake packet. fix in the works... anyways, yes, you need to update both peers to current cvs. Lars Ellenberg