[DRBD-user] System is syncing - but - drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295

Dan Didier dan at mapolce.com
Tue Aug 31 17:08:36 CEST 2004


Hello again all - syncing is happening - see output of cat /proc/drbd:

[root at linux1 src]# cat /proc/drbd
version: 0.7.2 (api:75/proto:74)
SVN Revision: 1483:1485 build by root at linux1.romestripsteel.local,
2004-08-31 10:44:30
 0: cs:SyncSource st:Primary/Secondary ld:Consistent
    ns:733696 nr:0 dw:0 dr:740000 al:0 bm:43 lo:0 pe:1180 ua:1576 ap:0
        [>...................] sync'ed:  1.6% (45825/46537)M
        finish: 8:08:48 speed: 1,536 (1,656) K/sec
 1: cs:Unconfigured
[root at linux1 src]#

However I am getting this error from dmesg:


drbd0: size = 48063896 KB
drbd0: 47654296 KB marked out-of-sync by on disk bit-map.
drbd0: No usable activity log found.
drbd0: drbdsetup [6789]: cstate Unconfigured --> StandAlone
drbd0: drbdsetup [6791]: cstate StandAlone --> Unconnected
drbd0: drbd0_receiver [6792]: cstate Unconnected --> WFConnection
drbd0: drbd0_receiver [6792]: cstate WFConnection --> WFReportParams
drbd0: Handshake successful: DRBD Network Protocol version 74
drbd0: Connection established.
drbd0: I am(S): 1:00000002:00000001:00000001:00000001:01
drbd0: Peer(S): 0:00000002:00000001:00000001:00000001:01
drbd0: drbd0_receiver [6792]: cstate WFReportParams --> WFBitMapS
drbd0: Secondary/Unknown --> Secondary/Secondary
drbd0: drbd0_receiver [6792]: cstate WFBitMapS --> SyncSource
drbd0: Resync started as SyncSource (need to sync 47654296 KB [11913574
bits set]).
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967294
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: Secondary/Secondary --> Primary/Secondary
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967294
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967294
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967294
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967295
drbd0: [drbd0_worker/6790] sock_sendmsg time expired, ko = 4294967294
[root at linux1 src]#

What do you think this could be caused from?  

Thanks again,
Dan




More information about the drbd-user mailing list