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/vgcreate/lvcreate/mkfs.ext3... don't forget to run lvchange -an vg0/ha_lv
nothing special about tagging is requires as far as I am aware.. you might need to look at filter section to ensure the volumes are not blacklisted.
On Tue, Dec 11, 2012 at 1:54 AM, Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx> wrote:
On Mon, 10 Dec 2012 23:36:51 +1100 yu song wrote:In my non-CLVMD configuration I use HA-LVM with these entries in cluster.conf
> 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.
<resources>
<lvm name="MYLV" vg_name="MYVG" lv_name="MYLV"/>
<fs device="/dev/MYVG/MYLV" force_fsck="0" force_unmount="1"
fsid="50001" fstype="ext3" mountpoint="/my_mnt" name="MYFS" options=""
self_fence="1"/>
...
<service domain="MYSRV" autostart="1" name="MYSRV">
<ip ref="x.y.w.z"/>
<lvm ref="MYLV"/>
<fs ref="MYFS"/>
....
and tagging in lvm.conf (volume_list directive)
With CLVMD and the config I'm testig with snapshots and "vgchange -cn"
I still don't use any GFSx file systems, only plain ext3, mounted only
on the node carrying on the service, and my configuration simply
doesn't contain the lvm part:
<resources>
<fs device="/dev/MYVG/MYLV" force_fsck="0" force_unmount="1"
fsid="50001" fstype="ext3" mountpoint="/my_mnt" name="MYFS" options=""
self_fence="1"/>
...
<service domain="MYSRV" autostart="1" name="MYSRV">
<ip ref="x.y.w.z"/>
<fs ref="MYFS"/>
....
Using locking_type=3 in lvm.conf while not using any tagging
(volume_list directive)
Any comments about that?
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
