<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="+1"><font face="Helvetica, Arial, sans-serif">Dear </font></font>Gábor!</p>
<p>Thank you so much!</p>
<p>This was exactly what I was looking for:<br>
</p>
<p>linstor resource toggle-disk hydra1 vm-118-disk-1 -s pool_drbd</p>
<p>Works like a charm.</p>
<p>Cheers,</p>
<p>Volker<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 03.12.20 07:32, Gábor Hernádi wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL16tNZOaOXh-5oY+M1D+oo9c5HXETd4AjJcy9LYoyvBRng8+A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi,<br>
<br>
> But all the volumes are now and remain in diskless state on
Hydra1?<br>
<br>
when you added the third node, the command `node create Hydra1`
triggered Linstor's auto-tiebreaker feature. DRBD can use
quorum[1] (useful if your cluster gets split), but needs 3 peers
for that (so there can be a majority of still connected nodes,
which is kinda difficult with only 2 peers). That is the reason
why Linstor automatically deploys all resources where you
already had 2 diskful replicas to the third as diskless peer.
You can also check the .res files to see that quorum is now
active on all your DRBD-resources.<br>
<br>
A Linstor-managed tiebreaking resource is by default
hidden/filtered in the `resource list`. You can still show them
with `resource list --all`.<br>
<br>
> But in the end the DRBD-Device is still diskless on Hydra1<br>
<br>
That will also stay this way until you tell Linstor to do
something differently.<br>
<br>
> How do I get the volumes also DRBD-replicated onto the
third node?<br>
<br>
Usually Linstor complains if you try to create a resource while
the resource is already deployed on the given node ("resource
already exists" or something like that). <br>
However, Linstor's tiebreaker is different as that one allows
you to either `resource create Hydra1 $resource -s ...` or do a
`resource toggle-disk Hydra1 $resource -s ...`, whereas for the
special case of Linstor tiebreakers, the first method will
internally be mapped to the second one :)<br>
<br>
For me everything looks normal / as expected.<br>
<br>
Best regards,<br>
Gabor<br>
<br>
<br>
[1] <a
href="https://www.linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-feature-quorum"
moz-do-not-send="true">https://www.linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-feature-quorum</a></div>
</blockquote>
<pre class="moz-signature" cols="72">--
=========================================================
inqbus Scientific Computing Dr. Volker Jaenisch
Hungerbichlweg 3 +49 (8860) 9222 7 92
86977 Burggen <a class="moz-txt-link-freetext" href="https://inqbus.de">https://inqbus.de</a>
=========================================================</pre>
</body>
</html>