[DRBD-user] Problems with DRBD9/drbdmanage

Robert Altnoeder robert.altnoeder at linbit.com
Tue Apr 12 15:06:52 CEST 2016

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

Hello Mr. Goryachev,

it is hard to say after the problem occurred, but generally speaking,
the drbdmanage server on the other node needs to see a DRBD9 event
happen on one of the other nodes to start performing changes.
If, for example, the drbdmanage server was not running on the other node
at the time the command was issued, or the drbd control resource was
disconnected at that time, then the system on the other side does not
see the event. However, upon receiving further events (e.g. due to
creating another volume, a node always tries to perform all pending actions.

If you only want to wake up any nodes that might have missed an event or
that have been started after the other nodes in the cluster performed
changes, you can also use the command "drbdmanage poke" to generate a
change event for all nodes (instead of e.g. creating a dummy volume).

Best regards,
Robert Altnoeder
DRBD - Corosync - Pacemaker
+43 (1) 817 82 92 - 0 <tel:43181782920>
robert.altnoeder at linbit.com <mailto:robert.altnoeder at linbit.com>
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

On 04/07/2016 12:02 PM, Adam Goryachev wrote:
> [... cut ...]
> ie, add a volume on the "other" node, and it magically found both new
> volumes and started syncing them both.
> So, I'm not sure why the issue happened in the first place, or why
> adding a second volume from the second server fixed it. Any advice
> would be appreciated,
> Regards,
> Adam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160412/75b28ba4/attachment.htm>

More information about the drbd-user mailing list