Ok, so for the time being I will have to stay with the 2 LVM backed nodes
or perhaps "convert" the 3rd node to LVM as well (even though that's
something I would like to avoid for now).
Thanks for your replies.
Regards,
Yannis
On Fri, 24 Aug 2018 at 11:23, Robert Altnoeder
wrote:
> On
On 08/24/2018 12:21 PM, Yannis Milios wrote:
> Thanks for you answer.
>
> It should be possible to avoid this by setting an explicit size
> for the
> DRBD volume in the resource configuration file, so that DRBD will only
> use that much space even if more is available.
>
>
> Do
Thanks for you answer.
It should be possible to avoid this by setting an explicit size for the
> DRBD volume in the resource configuration file, so that DRBD will only
> use that much space even if more is available.
Do you mean by manually editing the resource configuration files in
On 08/24/2018 08:54 AM, Yannis Milios wrote:
> "[81307.730199] drbd test/0 drbd1000 pve3: The peer's disk size is too
> small! (20971520 < 20975152 sectors)
>
> This is reproducible in all my attempts to create any random resource
> on the 3rd node. Could this be happening due to the alignment
Hello,
Trying to create a new resource by using Linstor, on a 3 node cluster. Two
of the nodes are using LVM thin as storage backend and one of them is using
ZFS.
I created a test RD, then a VD with a size of 10GB. Then, I create the
resource on the LVM backed nodes by using 'linstor r c test'
