Marco Marino writes:
> Ferenc, regarding the flag use_lvmetad in
> /usr/lib/ocf/resource.d/heartbeat/LVM I read:
>
>> lvmetad is a daemon that caches lvm metadata to improve the
>> performance of LVM commands. This daemon should never be used when
>> volume groups exist
Ferenc, regarding the flag use_lvmetad in
/usr/lib/ocf/resource.d/heartbeat/LVM I read:
"#lvmetad is a daemon that caches lvm metadata to improve the
# performance of LVM commands. This daemon should never be used when
# volume groups exist that are being managed by the
Marco Marino writes:
> I agree with you for
> use_lvmetad = 0 (setting it = 1 in a clustered environment is an error)
Where does this information come from? AFAIK, if locking_type=3 (LVM
uses internal clustered locking, that is, clvmd), lvmetad is not used
anyway, even if
Hi Bliu, thank you.
I agree with you for
use_lvmetad = 0 (setting it = 1 in a clustered environment is an error)
but I think I have to set
locking_type = 3 only if I use clvm
In my case, I'm trying to use LVM so I think that locking_type = 1 is ok.
What do you think about?
Furthermore, I have an
On 01/18/2017 04:45 PM, Marco Marino wrote:
Hi, I'm trying to realize a cluster with 2 nodes that manages a volume
group.
Basically I have a san connected to both nodes that exposes 1 lun. So
both nodes have a disk /dev/sdb. From one node I did:
fdisk /dev/sdb <- Create a partition with
Hi, I'm trying to realize a cluster with 2 nodes that manages a volume
group.
Basically I have a san connected to both nodes that exposes 1 lun. So both
nodes have a disk /dev/sdb. From one node I did:
fdisk /dev/sdb <- Create a partition with type = 8e (LVM)
pvcreate /dev/sdb1
vgcreate myvg