[DRBD-user] Device verification always fails with timeout

Lars Ellenberg lars.ellenberg at linbit.com
Fri Jul 4 14:25:51 CEST 2014

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


On Mon, Jun 30, 2014 at 10:35:38AM +0400, Igor Novgorodov wrote:
> Hello everyone, i need some help.
> 
> I've got 2 servers in DRBD mirror, replication link is 4x1Gbit in
> balance-rr bond, resulting in about 3.8 Gbit/s as measured by iperf.
> No errors on interfaces at all, the replication never fails under
> normal conditions, it's been up for almost a year.
> 
> But when i decide to do a verification of a DRBD device, it goes
> fine for some time (each time different), but then it fails.
> Kernel is 3.4.42, DRBD is built as external module version 8.4.3

Upgrade your DRBD module.

While this is a typical standard answer,
it will in fact help.

What happened is what I call a distributed resource starvation deadlock,
and it has been fixed since.

> Any help would be appreciated.
> 
> dmesg:
> [129075.674385] block drbd0: conn( Connected -> VerifyS )
> [129075.674416] block drbd0: Starting Online Verify from sector 44054936
> [132983.906214] d-con VM_STORAGE2_1: [drbd_w_VM_STORA/3871]
> sock_sendmsg time expired, ko = 6

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list   --   I'm subscribed



More information about the drbd-user mailing list