Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello @list! I use drbd 0.7.21 on SUSE prof 10.1. I configured it and when I starting the drbd, everything looks fine, but when It starting to sync it works fine about 10 sec and then crash. Between the two PC I use Cat 6 cross 1000 Mb/s cable. Before the crash I can ping the onother node on the drbd interface but after the crash I can't!!! And there isn't any link down message in the logs. The logs: A-node: Dec 8 16:42:09 ta-fs-a kernel: drbd0: Secondary/Secondary --> Primary/Secondary Dec 8 16:42:09 ta-fs-a kernel: drbd0: I am(P): 1:00000002:00000001:00000001:00000001:11 Dec 8 16:42:09 ta-fs-a kernel: drbd0: Peer(S): 0:00000001:00000001:00000001:00000001:01 Dec 8 16:42:09 ta-fs-a kernel: drbd0: drbd0_receiver [15141]: cstate Connected --> WFBitMapS Dec 8 16:42:10 ta-fs-a kernel: drbd0: drbd0_receiver [15141]: cstate WFBitMapS --> SyncSource Dec 8 16:42:10 ta-fs-a kernel: drbd0: Resync started as SyncSource (need to sync 585805808 KB [146451452 bits set]). Dec 8 16:42:48 ta-fs-a kernel: drbd0: sock was reset by peer Dec 8 16:42:48 ta-fs-a kernel: drbd0: _drbd_send_page: size=4096 len=2092 sent=-32 Dec 8 16:42:48 ta-fs-a kernel: drbd0: drbd_send_block() failed Dec 8 16:42:48 ta-fs-a kernel: drbd0: drbd0_worker [11895]: cstate SyncSource --> NetworkFailure Dec 8 16:42:48 ta-fs-a kernel: drbd0: drbd0_receiver [15141]: cstate NetworkFailure --> BrokenPipe Dec 8 16:42:48 ta-fs-a kernel: drbd0: short read expecting header on sock: r=-104 Dec 8 16:42:48 ta-fs-a kernel: drbd0: meta connection shut down by peer. Dec 8 16:42:48 ta-fs-a kernel: drbd0: asender terminated Dec 8 16:42:48 ta-fs-a kernel: drbd0: worker terminated Dec 8 16:42:48 ta-fs-a kernel: drbd0: ASSERT( mdev->ee_in_use == 0 ) in drivers/block/drbd/drbd_receiver.c:1880 Dec 8 16:42:48 ta-fs-a kernel: drbd0: drbd0_receiver [15141]: cstate BrokenPipe --> Unconnected Dec 8 16:42:48 ta-fs-a kernel: drbd0: Connection lost. Dec 8 16:42:48 ta-fs-a kernel: drbd0: drbd0_receiver [15141]: cstate Unconnected --> WFConnection B-node: Dec 8 16:42:09 ta-fs-b kernel: drbd0: Secondary/Secondary --> Secondary/Primary Dec 8 16:42:10 ta-fs-b kernel: drbd0: drbd0_receiver [29882]: cstate WFBitMapT --> SyncTarget Dec 8 16:42:10 ta-fs-b kernel: drbd0: Resync started as SyncTarget (need to sync 585805808 KB [146451452 bits set]). Dec 8 16:42:48 ta-fs-b kernel: drbd0: magic?? m: 0x0 c: 0 l: 0 Dec 8 16:42:48 ta-fs-b kernel: drbd0: ASSERT( mdev->cstate < Connected ) in drivers/block/drbd/drbd_receiver.c:1836 Dec 8 16:42:48 ta-fs-b kernel: drbd0: asender terminated Dec 8 16:42:48 ta-fs-b kernel: drbd0: drbd_send_drequest() failed, aborting...<6>drbd0: drbd0_worker [16191]: cstate SyncTarget --> NetworkFailure Dec 8 16:42:48 ta-fs-b kernel: drbd0: worker terminated Dec 8 16:42:48 ta-fs-b kernel: drbd0: drbd0_receiver [29882]: cstate NetworkFailure --> Unconnected Dec 8 16:42:48 ta-fs-b kernel: drbd0: Connection lost. Dec 8 16:42:48 ta-fs-b kernel: drbd0: drbd0_receiver [29882]: cstate Unconnected --> WFConnection What is it mean magic?? in the B-node's log??? Thanks, Balázs