[DRBD-user] DRBD full sync is stalled

Jeroen Groenewegen van der Weyden groen692 at grosc.com
Mon Sep 28 13:03:26 CEST 2009

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


Thank you, I hear what you are saying.

One more thing I noticed when testing with DRBD 8.3.3RC2 the behaviour 
is different. The target machine does not stall but simply disconnects 
all network interfaces. The var/log/messages show the included in the 
snippet below.

Do you think with this information the bnx2 module is faulty?

mfg,
jeroen


------------------ snippet -------------------------
Sep 25 11:33:23 Cluster3Node1 kernel: block drbd1: Restarting receiver 
thread
Sep 25 11:33:23 Cluster3Node1 kernel: block drbd1: receiver (re)started
Sep 25 11:33:23 Cluster3Node1 kernel: block drbd1: conn( Unconnected -> 
WFConnection )
Sep 25 11:38:14 Cluster3Node1 kernel: ------------[ cut here ]------------
Sep 25 11:38:14 Cluster3Node1 kernel: WARNING: at 
net/sched/sch_generic.c:219 dev_watchdog+0x139/0x1eb()
Sep 25 11:38:14 Cluster3Node1 kernel: NETDEV WATCHDOG: eth0 (bnx2): 
transmit timed out
Sep 25 11:38:14 Cluster3Node1 kernel: Modules linked in: drbd(N) joydev 
ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit xt_physdev netbk blkbk 
blktap xenbus_be binfmt_misc bridge stp ip6t_REJECT nf_conntrack_ipv6 
ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter 
ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack 
ip_tables ip6table_filter ip6_tables x_tables ipv6 microcode fuse loop 
dm_mod ppdev 8250_pnp rtc_cmos rtc_core 8250 parport_pc floppy iTCO_wdt 
rtc_lib parport serial_core pcspkr sr_mod iTCO_vendor_support bnx2 e1000 
i2c_i801 container serio_raw i5000_edac i2c_core button edac_core shpchp 
pci_hotplug sg usbhid hid ff_memless ehci_hcd uhci_hcd usbcore sd_mod 
crc_t10dif xenblk cdrom xennet megaraid_sas edd ext3 mbcache jbd fan 
ide_pci_generic piix ide_core ata_generic ata_piix libata scsi_mod dock 
thermal processor thermal_sys hwmon [last unloaded: drbd]
Sep 25 11:38:14 Cluster3Node1 kernel: Supported: No
Sep 25 11:38:14 Cluster3Node1 kernel: Pid: 0, comm: swapper Tainted: 
G          2.6.27.21-0.1-xen #1
Sep 25 11:38:14 Cluster3Node1 kernel:
Sep 25 11:38:14 Cluster3Node1 kernel: Call Trace:
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8020c597>] 
show_trace_log_lvl+0x41/0x58
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff804635e0>] 
dump_stack+0x69/0x6f
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff80232991>] 
warn_slowpath+0xa9/0xd1
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff80406670>] 
dev_watchdog+0x139/0x1eb
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8023c2f2>] 
run_timer_softirq+0x1ba/0x268
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff80238543>] 
__do_softirq+0xa1/0x148
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8020c00c>] 
call_softirq+0x1c/0x28
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8020d2b3>] 
do_softirq+0x4b/0xca
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8020bace>] 
do_hypervisor_callback+0x1e/0x30
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff802073aa>] 
0xffffffff802073aa
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8020da6b>] 
xen_safe_halt+0x97/0xac
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff80210702>] 
xen_idle+0x2e/0x67
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff8020a422>] 
cpu_idle+0x57/0x93
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff80712a65>] 
start_kernel+0x3be/0x3ca
Sep 25 11:38:14 Cluster3Node1 kernel:  [<ffffffff807121e4>] 
x86_64_start_kernel+0xb4/0xba
Sep 25 11:38:14 Cluster3Node1 kernel:
Sep 25 11:38:14 Cluster3Node1 kernel: ---[ end trace 4f7e0b535ea49a76 ]---
Sep 25 11:38:14 Cluster3Node1 kernel: bnx2: eth0 NIC Copper Link is Down
Sep 25 11:38:14 Cluster3Node1 kernel: br0: port 1(eth0) entering 
disabled state
Sep 25 11:58:15 Cluster3Node1 -- MARK --
------------------ snippet -------------------------

mfg,

Jeroen.

Lars Ellenberg wrote:
>> The problems happens on Fujitsu Siemens server RX200/RX300. The total
>> of Fujistu Siemens Servers having this problem is 6 in total.
>> Other servers I have installed do not have this problem.
>>     
>
> Then this is a strong indication it is _not_ DRBD.
> What about fixing your network drivers or hardware, then?
>
> try Firmware update, kernel upgrade, NIC driver module upgrade, etc.
>
>   
>> The Fujistu Siemens server have onboard Broadcom interfaces "NIC:
>> NetXtreme II BCM5708 Gigabit Ethernet".
>>     
>
>   
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.409 / Virus Database: 270.13.113/2399 - Release Date: 09/27/09 17:52:00
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090928/28998d5b/attachment.htm>


More information about the drbd-user mailing list