[DRBD-user] Re: sock_sendmsg time expired

Lars Ellenberg Lars.Ellenberg at linbit.com
Thu Jul 13 19:47:01 CEST 2006

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


/ 2006-07-13 17:25:07 +0200
\ CHARTON Yannick:
> Hi,
> 
> I'm using drbd 0.7.17 to synchronise two nodes
> About each day, I suddently have a flow of messages on the primary :
> kernel: drbd0: [kjournald/2927] sock_sendmsg time expired, ko = 4294967295
> kernel: drbd0: [kjournald/2927] sock_sendmsg time expired, ko = 4294967294
> ...
> (I'm using a dedicated gigabyte link between the two nodes and a new cable)
> 
> When I restart the drbd service on the secondary, and after the synchronisation, it's okay. However, it starts again 1 or 2 days after.
> 
> All drbd.conf parameters are set to very common values.
> 
> What does the problem seem to be ?

broken NIC?

> Another thing : i'm using Heartbeat, and sometimes I receive the following message :
> 09:10:27 heartbeat: [2596]: WARN: 1 lost packet(s) for [secondary-server] [78569:78571]
> 09:10:27 primary-server heartbeat: [2596]: info: No pkts missing from secondary-server!

broken NIC!
(or chipset or driver, or interrupt confused, or some such...)

-- 
: Lars Ellenberg                                  Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :
__
please use the "List-Reply" function of your email client.



More information about the drbd-user mailing list