node1 (node inquorate):
[root@node1 ~]# vgs -o tags,vg_name
VG Tags VG
node1-hb vg00
vg_www
node2-hb vg_jabber
vg_postgres
vg_qdisk
vg_tomcat
node2 (quorate)
[root@node2 ~]# vgs -o tags,vg_name
VG Tags VG
vg00
vg_emasweb
node2-hb vg_jabber
vg_postgres
vg_qdisk
vg_tomcat
It's true that vg_qdisk has the label of node2-hb. But it's in the volume_list.
Regards, Javier
[root@node1 ~]# vgs -o tags,vg_name
VG Tags VG
node1-hb vg00
vg_www
node2-hb vg_jabber
vg_postgres
vg_qdisk
vg_tomcat
node2 (quorate)
[root@node2 ~]# vgs -o tags,vg_name
VG Tags VG
vg00
vg_emasweb
node2-hb vg_jabber
vg_postgres
vg_qdisk
vg_tomcat
It's true that vg_qdisk has the label of node2-hb. But it's in the volume_list.
Regards, Javier
Hello Javier
Can you send the ouput of this command for every node?
vgs -o tags,vg_name
2012/6/20 Javier Vela <jvdiago@xxxxxxxxx>
In the lvm.conf I have in volume_list the name of the vg_qdisk so this volume group should be available to both nodes at the same time.
My volume_list in lvm.conf:
node1:
volume_list = [ "vg00", "vg_qdisk", "@node1-hb" ]
node2:
volume_list = [ "vg00", "vg_qdisk", "@node2-hb" ]
Moreover with the comand lvdisplay I can see that the lv is available to both nodes. But maybe is worth to try another qdisk without lvm.
Hi.
Since you have HA-LVM, are you using volume tagging ? I noticed that your quorum disk belongs to a volume group vg_qdisk and I think when the first node that will activate the volumegroup will not allow the second node to activate the volumegroup because of volume tagging, so remove the quorumdisk from the volumegroup and just use it as a physical volume.
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
esta es mi vida e me la vivo hasta que dios quiera
-- 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
