Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 11.04.2012, at 1:16, Dan Barker wrote: > That is part of the story. You most likely have some protocol issues (thus > the log entries). > > Why would you experiment with cross-version drbd? You should have the > easiest results with both servers at the same, recent level. I'm not. I'm using exactly the same drbd version on both servers. Furthermore, I'm using exactly the same linux distro and kernel version (CentOS 6, 2.6.32-220.7.1). > You would need to verify the kernel module and userland program versions on > both servers, the commands run, and the relevant dmesg logs from both sides > for folks to help you on this problem. As I mentioned previously, both server had drbd 8.4.1. 8.3.11 and 8.3.12 are affected too. I posted log from Primary before, log on Secondary doesn't have anything interesting: >> Apr 10 11:13:54 web_backup kernel: block drbd0: Becoming sync target due to disk states. >> Apr 10 11:13:54 web_backup kernel: block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate ) >> Apr 10 11:13:54 web_backup kernel: block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 25(1), total 25; compression: 100.0% >> Apr 10 11:13:54 web_backup kernel: block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 25(1), total 25; compression: 100.0% >> Apr 10 11:13:54 web_backup kernel: block drbd0: conn( WFBitMapT -> WFSyncUUID ) >> Apr 10 11:13:54 web_backup kernel: block drbd0: updated sync uuid C237DF3A275A375A:0000000000000000:0000000000000000:0000000000000000 >> Apr 10 11:13:54 web_backup kernel: block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 >> Apr 10 11:13:54 web_backup kernel: block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0) >> Apr 10 11:13:54 web_backup kernel: block drbd0: conn( WFSyncUUID -> SyncTarget ) >> Apr 10 11:13:54 web_backup kernel: block drbd0: Began resync as SyncTarget (will sync 15519040 KB [3879760 bits set]). >> Apr 10 11:13:54 web_backup kernel: d-con r0: sock was shut down by peer >> Apr 10 11:13:54 web_backup kernel: d-con r0: peer( Primary -> Unknown ) conn( SyncTarget -> BrokenPipe ) pdsk( UpToDate -> DUnknown ) >> Apr 10 11:13:54 web_backup kernel: d-con r0: short read (expected size 16) >> Apr 10 11:13:54 web_backup kernel: d-con r0: asender terminated >> Apr 10 11:13:54 web_backup kernel: d-con r0: Terminating asender thread > Are you aware that if you do not care about the contents of the disks, you > don't have to sync all the zeros? I didn't know that, thanks. But still, there is clearly something wrong, and I'm sure this problem will appear not only during initial sync, but also during normal operation.