<div dir="ltr">If you want diskful replicas on all nodes, you also need to change your place-count on your used resource group.<div>Otherwise it will always only be diskful on 2 nodes (which ones are decided by linstor).</div><div><br></div><div>Cheers,</div><div>Rene</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 3, 2020 at 7:33 AM Gábor Hernádi <<a href="mailto:gabor.hernadi@linbit.com">gabor.hernadi@linbit.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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" target="_blank">https://www.linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-feature-quorum</a></div>
_______________________________________________<br>
Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote></div>