[DRBD-user] DRPD + DOPD Not Recovering from Replication Link Failure

Art Age Software artagesw at gmail.com
Mon Jul 14 08:58:52 CEST 2008

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

On Sun, Jul 13, 2008 at 11:48 PM, Florian Haas <florian.haas at linbit.com> wrote:
> Art Age Software wrote:
>> I have set up drbd + dopd according to the User's Guide and am
>> attempting to test according to the instructions as follows:
>> 1. "To test whether your dopd setup is working correctly, interrupt
>> the replication link of a configured and connected resource while
>> Heartbeat services are running normally. You may do this by either
>> physically unplugging the network link, or by running ifconfig
>> interface down on the interface used for DRBD replication."
>> OK, I successfullly bring down the replication interface (via ifconfig).
> Wrong approach. :-)
> If you do ifconfig down; DRBD will terminate its networking threads,
> putting the resource in StandAlone mode. You won't get it out of
> StandAlone until you do "drbdadm connect".
> If, conversely, you pull the cable, or insert an iptables rule to drop
> incoming DRBD packets, DRBD's networking threads will continue to run
> and the resource will remain in WFConnection on both ends. The resource
> will then return to Connected mode as soon as you re-plug the cable or
> remove the iptables rule.
> Florian

OK, thanks. You might want to update the User's Guide and your blog
post, both of which suggest "ifconfig down" to simulate the failure.

More information about the drbd-user mailing list