[DRBD-user] Kernel Oops, RH9.0, 2.4.20-19.9

Lars Ellenberg Lars.Ellenberg at linbit.com
Mon Jun 14 09:40:47 CEST 2004

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


/ 2004-06-13 21:39:38 -0700
\ Tim Hasson:
> Here's the results after I upgraded to kernel 2.4.26 from kernel.org (also
> recompiled drbd 0.6.12)
> 
> 
> 
                                                                               |
.--- slightly edited syslog:
| drbd: ===> drbd start <===
| drbd: modprobe -s drbd minor_count=2
| kernel: drbd: initialised. Version: 0.6.12 (api:64/proto:62)
| kernel: drbd0: Creating state file
| kernel: "/var/lib/drbd/drbd0"
| kernel: klogd 1.4.1, ---------- state change ----------
| kernel: drbd1: Creating state file
| kernel: "/var/lib/drbd/drbd1"
| kernel: drbd0: Connection established. size=35277516 KB / blksize=4096 B
| kernel: drbd1: Connection established. size=35277516 KB / blksize=4096 B
| drbd: drbdsetup /dev/nb1 wait_connect -t 0
| drbd: 'drbd0' SyncingAll, waiting for this to finish
| drbd: 'drbd1' SyncingAll, waiting for this to finish
| drbd: drbdsetup /dev/nb0 wait_sync
| drbd: drbdsetup /dev/nb1 wait_sync
| 
| about one minute later:
| 
| kernel: KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || \
| 		(flags&(MSG_PEEK|MSG_TRUNC))) failed at tcp.c(1603)
| last message repeated 11 times
| kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
| kernel: KERNEL: assertion (skb==NULL || before(tp->copied_seq, \
| 		TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
| kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
| kernel: KERNEL: assertion (skb==NULL || before(tp->copied_seq, \
| 		TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
| kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
| kernel: KERNEL: assertion (skb==NULL || before(tp->copied_seq, \
| 		TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
| kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
| last message repeated 3 times
`---

> Any ideas?

your NIC is broken and cannot stand the load of a drbd full sync anymore.
I bet you can crash that box by just running a 
 netcat -l -p 7777 > /dev/null < /dev/null # on drbd2
and do a
 netcat drbd2 7777 < /dev/zero     # from drbd1 or any other box...


	Lars Ellenberg



More information about the drbd-user mailing list