[DRBD-user] How can web100 block drbd?

Andreas J. Koenig andreas.koenig.gmwojprw at franz.ak.mind.de
Mon Apr 3 14:55:07 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.

>>>>> On Mon, 3 Apr 2006 02:28:48 -0500, Maurice Volaski <mvolaski at aecom.yu.edu> said:

  > Web100 is a patch to the Linux kernel (see http://www.web100.org) that
  > enables one to get statistics on all TCP traffic. There was a bug in
  > the previous posted version, 2.5.8, but the author seems to have fixed
  > it.

  > So as far I can tell, all network traffic works except for drbd!

  > The computer running drbd (0.7.17 under kernel has web100
  > and displays this message when it should be receiving data from its
  > peer (the acting primary):

  > <3>[14938.140724] drbd1: [drbd1_receiver/8822] sock_sendmsg time
  > expired, ko = 4294967295

  > (Interestingly, the peer won't let me access the drbd disks; they appear hung)

  > The author is not convinced web100 is responsible. He believes it is
  > possible that web100 alters timing that somehow could be triggering a
  > bug elsewhere in the kernel, including in drbd.

  > Any comments?

I'm having a hard time setting 0.7.17 up with 2.6.16. Specifically,
I'm seeing

drbd0: [drbd0_receiver/25303] sock_sendmsg time expired, ko = 4294967295

all over the place and I have applied the patch that Lars posted a few
days ago on the list that I thought was addressing this issue and I
have no web100.

Unfortunately this is my first time to integrate heartbeat and DRBD,
so it's quite possible that I made a pilot error. I'll switch to the
SVN version now and start from scratch and will report what I find.


More information about the drbd-user mailing list