<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello Mr. Goryachev,<br>
<br>
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.<br>
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.<br>
<br>
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).<br>
<br>
Best regards,<br>
-- <br>
<div class="moz-signature"> Robert Altnoeder<br>
DRBD - Corosync - Pacemaker<br>
<a href="tel:43181782920"
style="color:#000000;text-decoration:none;">+43 (1) 817 82 92
- 0</a><br>
<a href="mailto:robert.altnoeder@linbit.com"
style="color:#000000;text-decoration:none;">robert.altnoeder@linbit.com</a><br>
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
</div>
<br>
On 04/07/2016 12:02 PM, Adam Goryachev wrote:<br>
</div>
<blockquote cite="mid:5706304C.3020705@websitemanagers.com.au"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
[... cut ...]<br>
<br>
ie, add a volume on the "other" node, and it magically found both
new volumes and started syncing them both.<br>
<br>
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,<br>
<br>
Regards,<br>
Adam<br>
<br>
<br>
</blockquote>
<br>
</body>
</html>