Not 100% sure but the first 'partition' could be where drbd stores metadata?
Your setup should be fine as long ad you can deal in an easy manner with
future resizing of the backing device (sde).
Yannis
root@iscsi2 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
...
Hi Roberto and all :-)
Do you mean LVL or LVM-thin ?
This is my storage-plugin: drbdmanage.storage.lvm.Lvm
I changed it from the default before creating drbdmanage cluster
So when I create a VM on node1, for example, could happen that the resource
is allocated on node2 and i get a diskless
Hi,
Thanks for the detailed explanation and sample examples.
I will work on suggestions about missing DRBD-Pacemaker, GFS2-Pacemaker
configuration and re-check fencing configuration and I will let you know
the results of my experiments.
--Raman
On Sat, Mar 25, 2017 at 5:48 AM, Igor Cicimov <
i
Hello,
This is just a note for the mailing list maintainer; it appears that
that's something wrong in threading on this ml archive.
I noted that my message:
http://lists.linbit.com/pipermail/drbd-user/2017-March/023117.html
Is incorrectly classified as a reply to :
http://lists.linbit.com/pipe
Il 25/03/2017 11:02, Den ha scritto:
> Hi,
Hi Den,
> I'm testing a 3 node cluster, fresh installed with linbit repo for pve
> with last versions
Me too (even if mine is not fresh installed ;-) )
> I have configured LVM as backend storage and set redundancy to 1 for now.
Do you mean LVL or LVM
Hi,
I'm testing a 3 node cluster, fresh installed with linbit repo for pve
with last versions
I have configured LVM as backend storage and set redundancy to 1 for now.
So when I create a VM on node1, for example, could happen that the resource
is allocated on node2 and i get a diskless resourc
Hi, I'm trying to understand how to configure raw devices when used with
drbd. I think I have a problem with data alignment. Let me describe my case:
I have a raw device /dev/sde on both nodes and on top of it there is the
drbd device. So, in the .res configuration file I have
disk
