Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
drbd-0.7-cvs current as of this morning does not longer on my setup. However the initial resync get stuck reliably. It syncs about 1% of the 2GB lvm volume and stalls.
primary:
sdev01:~# cat /proc/drbd
version: 0.7-pre6 (api:72/proto:72)
0: cs:SyncSource st:Primary/Secondary ld:Consistent
ns:15988 nr:0 dw:0 dr:15988 al:0 bm:1 lo:0 pe:0 ua:0
[>...................] sync'ed: 1.3% (1332/1348)M
finish: 21:03:33 speed: 17 (17) K/sec
sysrq-t:
drbd0_receive D 00000092 0 3152 1 3156 2284 (L-TLB)
f1e9ff08 00000046 00000003 00000092 f1e9fed0 00000092 f7ad6260 00000000
f7a8a320 f7a9ac00 c3e96480 00000001 f213c46c f213c000 00000286 f1e9e000
f7a9ac00 c1a0cbe0 000f4240 89014b40 000f4383 f3cf1048 f213c000 00000000
Call Trace:
[<f8def5a8>] drbd_get_ee+0x1c8/0x330 [drbd]
[<c011e270>] default_wake_function+0x0/0x20
[<f8df106a>] receive_DataRequest+0xca/0x290 [drbd]
[<f8deff7d>] drbd_recv_header+0x1d/0xe0 [drbd]
[<f8df20e2>] drbdd_init+0xb2/0x6c0 [drbd]
[<c0124d34>] daemonize+0xa4/0xb0
[<f8de92cd>] drbd_thread_setup+0x3d/0x60 [drbd]
[<f8de9290>] drbd_thread_setup+0x0/0x60 [drbd]
[<c0106005>] kernel_thread_helper+0x5/0x10
#addr2line -e drivers/block/drbd/drbd.ko 85A8
/usr/src/linux-2.6.5-vs/drivers/block/drbd/drbd_receiver.c:277
drbd0_asender S DA02AA90 0 3156 1 3157 3152 (L-TLB)
f1e41da4 00000046 00000003 da02aa90 f1ee76a0 00000001 f49a56a0 c0261f80
00000007 f44c21fc 00000000 00000001 00000020 f1e40000 f1e41db8 f1e41da4
00000246 c1a0cbe0 00000000 1de9e000 000f43e8 f3cf1608 001bf290 f1e41db8
Call Trace:
[<c0261f80>] tcp_rcv_established+0x160/0x770
[<c012c0fe>] schedule_timeout+0x5e/0xb0
[<c012c090>] process_timeout+0x0/0x10
[<c025a7b9>] tcp_recvmsg+0x779/0x8e0
[<c0120940>] autoremove_wake_function+0x0/0x40
[<c0120940>] autoremove_wake_function+0x0/0x40
[<c027cf66>] inet_recvmsg+0x46/0x70
[<c022e0f5>] sock_recvmsg+0x85/0x110
[<f8de99d5>] _drbd_send_cmd+0xb5/0x150 [drbd]
[<f8df2f35>] drbd_asender+0x195/0x42e [drbd]
[<c010704b>] __down_failed+0xb/0x14
[<f8de92cd>] drbd_thread_setup+0x3d/0x60 [drbd]
[<f8de9290>] drbd_thread_setup+0x0/0x60 [drbd]
[<c0106005>] kernel_thread_helper+0x5/0x10
drbd0_worker S 00000096 0 3157 1 3190 3156 (L-TLB)
f1e9bf50 00000046 00000003 00000096 007c00a0 00000000 f49a5ae0 00000001
00000001 00000001 00000000 00000000 00000000 f1e9beec f8ded0e0 00000001
f1e9bedc c1a14be0 00000000 f478e400 000f4383 f3cf1bc8 f1e9a000 f213c158
Call Trace:
[<f8ded0e0>] drbd_md_io_complete+0x0/0x30 [drbd]
[<c01072b1>] __down_interruptible+0xa1/0x160
[<c011e270>] default_wake_function+0x0/0x20
[<c010705e>] __down_failed_interruptible+0xa/0x10
[<f8deee81>] .text.lock.drbd_dsender+0x10b/0x14a [drbd]
[<f8de92cd>] drbd_thread_setup+0x3d/0x60 [drbd]
[<f8de9290>] drbd_thread_setup+0x0/0x60 [drbd]
[<c0106005>] kernel_thread_helper+0x5/0x10
Any ideas?
Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAfP3fbukMzn5TCZERAi65AJ0XFCAaiAcpQGbgTs5G5lY59bM29wCfb1gf
HNzrzQ6EnmWkqWbmqKmPLQA=
=3BC7
-----END PGP SIGNATURE-----