[Drbd-dev] DRBD Bug Report : DRBD 9.0 after-resync-target not being called after resync / reconnect

Lars Ellenberg lars.ellenberg at linbit.com
Wed Apr 4 12:37:26 CEST 2018

On Wed, Apr 04, 2018 at 10:04:49AM +0300, Farhan Khan wrote:
> Hello, I would like to report a bug:
> Scenario:
> - 2 nodes running as primary and secondary on CentOS 7.4 with pacemaker and
> corosync with dedicated link Gigabit link between nodes
> Bug description and replication:
> - Disconnect the link between nodes
>      --> fence-peer is called and secondary node is correctly fenced
> - Do not write any new data to primary while the link is broken
> -Reconnect the link
>      --> nodes reconnect and re-sync correctly
>      --> after-resync-target is NOT called and location constraint remains

Becaquse it likely did not sync anything, because there was nothing to
sync, it did not become sync target, so there was nothing to do for an
"after" resync target handler?

You should use the "unfence-peer" handler to unfence.

: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker
: R&D, Integration, Ops, Consulting, Support

DRBD® and LINBIT® are registered trademarks of LINBIT

More information about the drbd-dev mailing list