[DRBD-user] DRBD keeps doing full resync

Lars Ellenberg lars.ellenberg at linbit.com
Tue Aug 18 18:59:18 CEST 2015

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

On Fri, Aug 14, 2015 at 05:00:48PM +1000, Viktor Villafuerte wrote:
> Hi all,
> I've got very similar problem to
> http://lists.linbit.com/pipermail/drbd-user/2015-July/022243.html
> that.
> OS: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> kernel: kernel-2.6.32-573.1.1.el6.x86_64
> DRBD: kmod-drbd84-8.4.6-1.el6.elrepo.x86_64
> Two node cluster where after upgrade to the lastest kernel + Corosync
> Pacemaker DRBD I've encoutered problems.

Did you upgrade both nodes yet?

> Secondary does a full resync, seems to successfully finish it but then
> 'PingAck did not arrive in time' happens and the resync repeats. This
> keeps happening in a loop thereafter.

You could increase the "ping timeout" for now,
and see if that gets you over this odd issue.

> Please note that I could not observe any network problems, no problems
> with the resync or any other services, except the very end of the
> resync.
> I've tried reboot the secondary (target) node, invalidating the data
> and forcing full resync by hand, wating about 4 rounds of the loop :)
> But to no avail.
> Currently I'm in process of downgrading the kernel to see what happens
> but as it's a production server this will take little time (outage) :/
> I'm also fairly new to DRBD so please point out anything obvious I may
> be missing.
> thanks
> v

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

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