Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi there, I am running drbd-0.7.22 on kernel 2.6.17.11 (including Vserver patch set v2.0.2-rc31), and I am using eth1 (tg3 driver on Broadcom BCM5780 Gigabit adapter) on a 2-node-cluster to synchronise the DRBD devices. This network interface is also used to pull backups across the two nodes, and when the link is under heavy load I observed that sometimes (every 5-6 days) DRBD loses its inter-node connection: Dec 5 05:40:45 wgr-host1 kernel: drbd0: [reiserfs/3/1830] sock_sendmsg time expired, ko = 3 Dec 5 05:40:48 wgr-host1 kernel: drbd0: [reiserfs/3/1830] sock_sendmsg time expired, ko = 2 Dec 5 05:40:51 wgr-host1 kernel: drbd0: [reiserfs/3/1830] sock_sendmsg time expired, ko = 1 Dec 5 05:40:54 wgr-host1 kernel: drbd0: reiserfs/3 [1830]: cstate Connected --> NetworkFailure Dec 5 05:40:54 wgr-host1 kernel: drbd0: drbd0_receiver [10068]: cstate NetworkFailure --> BrokenPipe Dec 5 05:40:54 wgr-host1 kernel: drbd0: short read expecting header on sock: r=-512 Dec 5 05:40:54 wgr-host1 kernel: drbd0: asender terminated Dec 5 05:40:54 wgr-host1 kernel: drbd0: worker terminated Dec 5 05:40:54 wgr-host1 kernel: drbd0: drbd0_receiver [10068]: cstate BrokenPipe --> Unconnected Dec 5 05:40:54 wgr-host1 kernel: drbd0: Connection lost. Dec 5 05:40:54 wgr-host1 kernel: drbd0: drbd0_receiver [10068]: cstate Unconnected --> StandAlone Dec 5 05:40:54 wgr-host1 kernel: drbd0: receiver terminated Is this a known behaviour, and is there anything I can do to remedy? Many thanks, Holger