Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Am Montag, 16. Februar 2004 11:51 schrieb Lars Ellenberg: > On Mon, Feb 16, 2004 at 11:24:01AM +0100, Felix Ide wrote: > > Hi Lars, > > > > I have increased ping-int to a really lousy large value (just for the fun > > of it ;) and now the primary system stalled, no more entries in syslog, > > nothing... :-( > > > > The last entry in syslog was: > > Feb 15 21:18:34 drbd1-bfd kernel: drbd0: [kupdated/7] sock_sendmsg > > returned -32 > > again, what does the syslog on the peer say? It says: Feb 15 21:18:39 drbd2-bfd kernel: drbd0: unknown packet type! 83740267:8374:0267 Feb 15 21:18:40 drbd2-bfd kernel: drbd0: Connection lost. Feb 15 21:18:56 drbd2-bfd kernel: drbd0: Connection established. size=26097472 KB / blksize=4096 B Feb 15 21:19:01 drbd2-bfd kernel: drbd0: [drbd_asender_0/3554] sock_sendmsg returned 0 Feb 15 21:19:01 drbd2-bfd kernel: drbd0: Connection lost. Feb 15 21:19:34 drbd2-bfd kernel: drbd0: Connection established. size=26097472 KB / blksize=4096 B > > Feb 15 21:18:50 drbd1-bfd kernel: drbd0: Connection lost. > > Feb 15 21:18:50 drbd1-bfd kernel: drbd0: Connection established. > > size=26097472 KB / blksize=4096 B > > Feb 15 21:18:50 drbd1-bfd kernel: drbd0: Synchronisation started blks=32 > > Feb 15 21:18:53 drbd1-bfd kernel: drbd0: transferlog too small!! > > oops! > increase it! What it the biggest possible value? When I increase it too much, it says drbd0: could not kmalloc transfer_log > > ko-count = 20 > > did you ever see some "ko-count=19 ... 18 ... 17" messages? nope, nothing like this. > > tl-size = 10000 <== still too small :( > > > > > > connect-int = 601 sec > > ping-int = 601 sec > > sndbuf-size = 262144 <== increase it. > > it is "safe" to increase it with protocol C. What does "safe" mean? ;-) Thanks, Felix