lvm part still needs to be specified in the service section if you want to
follow a proper way.
locking_type =3 is correct.. you can use lvmconf --enable-cluster to
enable clvmd, which actually does change locking type to 3 anyway.
when you create a new vg controlled by clvmd.. after
pvcreate/vg
On Mon, 10 Dec 2012 23:36:51 +1100 yu song wrote:
> ok..firstly confirm whether you are using HA-LVM, not GFS/GFS2 .. correct?
> if ha-lvm, your vg should only be imported/mounted on one node, instead of
> multiple nodes.
In my non-CLVMD configuration I use HA-LVM with these entries in cluster.
On Mon, 10 Dec 2012 21:02:19 +1100 Yu wrote:
> vgchange -cn vgname
> Can disable cluster flag
> Regards
> Yu
Ok, thanks, I thought about this option too and it seems it works.
More testing in place.
In this cluster I have many services and each one is bundled with its
own VGs, so that each node is
Vgchange -cn vgname
Can disable cluster flag
Regards
Yu
On 10/12/2012, at 19:02, Gianluca Cecchi wrote:
> Hello, I was evaluating migration from a rhel 5.8 two node cluster with
> services based on ha-lvm to a clvmd one.
> I'm using netapp storage with snapshot technology.
> I quiesce db, the
Hello, I was evaluating migration from a rhel 5.8 two node cluster with
services based on ha-lvm to a clvmd one.
I'm using netapp storage with snapshot technology.
I quiesce db, then make a snapshot and then a third server connects to the
flashcopy volume, with "snapdrive connect" command and makes
