<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/27/20 7:54 PM, Rob Tongue wrote:<br>
</div>
<blockquote type="cite"
cite="mid:80c621d2-4b3e-b9f8-721c-fc12c50fc995@neverserio.us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><br>
</p>
<div class="moz-cite-prefix">On 1/27/20 10:57 AM, Rob Tongue
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d49d757a-a9d9-dc27-5052-8688a57fb53f@neverserio.us">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
One last tidbit, drbdadm status shows this for the resource I
created in proxmox from tank1 without the diskless storage-pools
created, and it is only showing up on tank1, not tank2 or tank3:
<p>vm-3000-disk-1 role:Primary<br>
disk:UpToDate<br>
tank2 role:Secondary<br>
<b> peer-disk:Diskless</b><br>
tank3 role:Secondary<br>
<b> peer-disk:Diskless</b><br>
</p>
<p>Not sure what to make of that. I am hesitant to blame the
proxmox plugin here, as I don't even see the devices listed in
/dev on 2 and 3. <br>
</p>
<br>
</blockquote>
I did (quite) a bit more research on what is happening here. The
peer-disks here that are listed as Diskless, are a result of me
adding --diskless-on-remaining for the resource-group, and are not
a result of the proxmox plugin. I can also see the created
resources via linstor volume list, and the diskless volumes are
indeed part of "DfltDisklessStorPool". Without that option,
resourced created only show up in tank1's device tree. So, I can
say with confidence now, that it's the proxmox plugin that is not
behaving as it should, or I have it configured incorrectly, as no
matter what I do, the storage node only appears on tank1 properly,
tank2 and tank3 show question marks, and I cannot see any drbd
resources within, nor get stats. How can I debug the plugin
further? Thanks in advance for any assistance that anyone can
provide. <br>
<br>
</blockquote>
I feel a little silly now, but it is what it is. It turns out, the
plugin IS actually working, the WebUI just isn't cooperating, but on
a hunch, I went through the motions of adding resources in this
exact setup, and they actually added fine, and I was able to migrate
resources around. So I'll chalk this up to the plugin still being
developed, and will eventually get fixed. Not only that, it does
serve as a reminder that the two nodes with question-marks ARE in
fact diskless, so there's that. :) Consider this one resolved for
now. <br>
</body>
</html>