[DRBD-user] drbd on virtio: WARNING: at block/blk-core.c

Thomas Vögtle thomas.voegtle at collax.com
Mon Nov 8 13:56:43 CET 2010

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


For testing purposes only I test our software and drbd stuff on two
Virtual Machines (kvm, virtio-net, virtio-blk)
I'm using Kernel

Since using drbd-8.3.9 I get following messages (or similar), again and
again, when DRBD is starting to sync:

[ 3830.713476] block drbd0: Began resync as SyncSource (will sync
7814892 KB [1953723 bits set]).
[ 3829.057557] block drbd0: helper command: /sbin/drbdadm
before-resync-target minor-0
[ 3830.739016] ------------[ cut here ]------------
[ 3830.739143] WARNING: at block/blk-core.c:337 blk_start_queue+0x29/0x42()
[ 3830.739145] Hardware name: Bochs
[ 3830.739147] Modules linked in: ocfs2 jbd2 ocfs2_nodemanager
ocfs2_stack_user ocfs2_stackglue dlm bonding dummy drbd cn 8021q garp
bridge stp llc rpcsec_gss_krb5 nfsd exportfs nfs lockd fscache nfs_acl
auth_rpcgss sunrpc xt_NOTRACK xt_TCPMSS xt_connmark xt_conntrack
xt_CONNMARK xt_state xt_policy iptable_nat nf_nat_tftp nf_conntrack_tftp
nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
nf_nat_irc nf_conntrack_irc nf_nat_sip nf_conntrack_sip nf_nat_ftp
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack
autofs4 xfrm_user ipmi_devintf ipmi_msghandler 8139too lcd_module ppdev
parport_pc parport st tpm_tis virtio_net tpm tpm_bios virtio_balloon
i2c_piix4 rtc_cmos i2c_core rtc_core rtc_lib evdev button sg [last
unloaded: ocfs2_stackglue]
[ 3830.739351] Pid: 22400, comm: path_id Not tainted #1
[ 3830.739353] Call Trace:
[ 3830.739355]  <IRQ>  [<ffffffff81183265>] ? blk_start_queue+0x29/0x42
[ 3830.739416]  [<ffffffff8104ccdb>] warn_slowpath_common+0x77/0x8f
[ 3830.739420]  [<ffffffff8104cd02>] warn_slowpath_null+0xf/0x11
[ 3830.739422]  [<ffffffff81183265>] blk_start_queue+0x29/0x42
[ 3830.739475]  [<ffffffff81239462>] blk_done+0xe0/0xfa
[ 3830.739514]  [<ffffffff81090d6e>] ? __rcu_process_callbacks+0xf2/0x2a6
[ 3830.739557]  [<ffffffff811f7a67>] vring_interrupt+0x27/0x30
[ 3830.739572]  [<ffffffff8108d3e9>] handle_IRQ_event+0x2d/0xb7
[ 3830.739575]  [<ffffffff8108f005>] handle_edge_irq+0xc1/0x102
[ 3830.739607]  [<ffffffff810133b5>] handle_irq+0x89/0x94
[ 3830.739610]  [<ffffffff8101326b>] do_IRQ+0x5a/0xab
[ 3830.739613]  [<ffffffff81011593>] ret_from_intr+0x0/0x11
[ 3830.739624]  <EOI>
[ 3830.739627] ---[ end trace a9e0f5d8de037953 ]---
[ 3830.739628] ------------[ cut here ]------------

I don't get any message like this on real hardware.

This is absolutely reproducable and still exists in git head

It didn't exist in

Except for the warning DRBD is syncing fine.

Any clues?


More information about the drbd-user mailing list