Hello, upgrading kernel on secondary from 2.6.36.2 to 2.6.37 gives me the following error on primary:
Jan 10 12:41:57 obelix kernel: block drbd0: BAD! BarrierAck #2350363662 received, expected #2350363661! Jan 10 12:41:57 obelix kernel: block drbd0: peer( Secondary -> Unknown ) conn( Connected -> ProtocolError ) pdsk( UpToDate -> DUnknown ) Jan 10 12:41:57 obelix kernel: block drbd0: short read expecting header on sock: r=-512 Jan 10 12:41:57 obelix kernel: block drbd0: Creating new current UUID Jan 10 12:41:57 obelix kernel: block drbd0: asender terminated Jan 10 12:41:57 obelix kernel: block drbd0: Terminating drbd0_asender Jan 10 12:41:57 obelix kernel: block drbd0: Connection closed Jan 10 12:41:57 obelix kernel: block drbd0: conn( ProtocolError -> Unconnected ) Jan 10 12:41:57 obelix kernel: block drbd0: receiver terminated Jan 10 12:41:57 obelix kernel: block drbd0: Restarting drbd0_receiver Jan 10 12:41:57 obelix kernel: block drbd0: receiver (re)started Jan 10 12:41:57 obelix kernel: block drbd0: conn( Unconnected -> WFConnection ) Jan 10 12:41:57 obelix kernel: block drbd0: Handshake successful: Agreed network protocol version 95 Jan 10 12:41:57 obelix kernel: block drbd0: conn( WFConnection -> WFReportParams ) Jan 10 12:41:57 obelix kernel: block drbd0: Starting asender thread (from drbd0_receiver [3233]) Jan 10 12:41:57 obelix kernel: block drbd0: data-integrity-alg: <not-used> Jan 10 12:41:57 obelix kernel: block drbd0: max_segment_size ( = BIO size ) = 65536 Jan 10 12:41:57 obelix kernel: block drbd0: drbd_sync_handshake: Jan 10 12:41:57 obelix kernel: block drbd0: self 28DDE63A9DEC9869:19CC15BDDB81CF01:8C9904DC3E8DFFD7:F46F8C2F00547891 bits:500 flags:0 Jan 10 12:41:57 obelix kernel: block drbd0: peer 19CC15BDDB81CF00:0000000000000000:8C9904DC3E8DFFD6:F46F8C2F00547891 bits:0 flags:0 Jan 10 12:41:57 obelix kernel: block drbd0: uuid_compare()=1 by rule 70 Jan 10 12:41:57 obelix kernel: block drbd0: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk( DUnknown -> UpToDate ) Upgrading the primary to 2.6.37 did also not help, it produces the same errors. I tried this on two different clusters and always the above error pops up if secondary is 2.6.37. Any idea what is wrong? Regards, Holger _______________________________________________ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
