[DRBD-user] drbd disconnets for no reason

Holger hwoehle at arcor.de
Mon Apr 23 13:03:16 CEST 2007

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hello,
from time to time if have a problem with unmotivated disconnects in my
heartbeat/drbd cluster.
cat /proc/drbd shows primary/unconnected resp. secondary/unconnected.
When i do a drbdadm connect all on the secondary drbd connects and does
a full-sync.
Following is a cut-off my logfiles:

Apr 19 14:37:39 zeus kernel: drbd0: [reiserfs/0/1101] sock_sendmsg time
expired, ko = 3
Apr 19 14:37:42 zeus kernel: drbd0: [reiserfs/0/1101] sock_sendmsg time
expired, ko = 2
Apr 19 14:37:45 zeus kernel: drbd0: [reiserfs/0/1101] sock_sendmsg time
expired, ko = 1
Apr 19 14:37:48 zeus kernel: drbd0:
/root/drbd-0.7.19/dist/BUILD/drbd-0.7.19/drbd/drbd_main.c:1089:
Connected flags=0x100a
Apr 19 14:37:48 zeus kernel: drbd0: short sent UnplugRemote size=8
sent=-1001
Apr 19 14:37:48 zeus kernel: drbd0: short read expecting header on sock:
r=-512

I am using version: 0.7.19 (api:78/proto:74) on both nodes.
Linux zeus 2.6.11.4-21.13-default/SuSE 9.3 on primary and Linux poseidon
2.6.16.27-0.6-default/OpenSuSE 10.1 on secondary

I haven't detected any other error neither on the machines nor in the
network.
Can i raise the debug-level of drbd ?

regards
Holger






More information about the drbd-user mailing list