Serviceguard 11.18 problem with VG version 2.1??

[boje]

Hi!

I was wondering if anyone have had any problems using Volume Group V2.1 in Serviceguard 11.18A cluster? I am trying to apply conf with one VG that is version 2.1. But only get this message:
Volume Group /dev/p01_vg01 is not found on any nodes in the cluster.

And if i try: vgchange -c y /dev/p01_vg01 i get this message:
vgchange: Cluster Services not available or unreachable on this system, for volume group "/dev/p01_vg01".

The cluster is running and i have one package running with a VG of version 1. And that package runs fine.

Br
Patrik

[Duncan Edmonstone · Accepted solution]

Patrik,

PHSS_38424 introduced support for LVM2.0 volume groups. I can find no evidence in the 2 newer patches to indicate that support for LVM2.1 volume groups has been added.

So the questions are:

i) Have you got that patch or a newer one on all your cluster nodes?
ii) Have you tried this with a 2.0 VG instead of 2.1?

HTH

Duncan

[boje]

Hi Duncan!

I did swlist -l product | grep PHSS_38 and did not find that patch.

I have not tried with VG version 2.0, only 1.0 and then 2.1.

I have no ignite server for these new machines that i am trying to config, so question is: Do i install this patch without a backup? The last thing i need is to reinstall thees 3 machines.

Br
Patrik

[Duncan Edmonstone]

Patrik,

PHSSS_38424 is superseded by PHSS_38861 which in turn is superseded by PHSS_39047, which is the latest patch for SG11.18. Check you don't have either of those patches as well.

As for patching without an Ignite backup... it's entirely up to you. The patch isn't kernel intrusive and doesn't require a reboot so I expect the chances of ending up with a hosed system are pretty low, but there may be patch dependencies to consider as well, so really its your call..

HTH

Duncan

[boje]

Thank you Duncan!

I will check for those patches and maybe install the latest. The VG is now v1.0 and will stay v1.0. But in the future i will need to make the vg´s v2.0 or v2.1.

Br
Patrik

[Emil Velez]

The patch seems to only affect serviceguard.

The symptoms are if you have a 2.0 VG if you do a cmquerycl it gives you a error or if you try to do a vgchange -c y to a lvm 2.0 VG it will also not work.

Note: it is also my understanding that LVM2.0 VGs cannot be used as a lock disk.

plus

if you use vxdisk -o alldgs list it will not see the lvm V2 volume group disks as owned by lvm.

The new diskowner command handles that. It is available as a patch.

I have worked extensively with this feature and previous comments about the patch are correct. Multiple patches include the LVMv2 functionality and then patch other items. Just get the lates SG and LVMv2 patch.

[boje]

Hi Emil!

The problem i experience is that you can not set the cluster bit on the 2.1VG. And the checkconf and applyconf does not recognize the 2.1VG on any node. Even doug i have done export and import as usual, only -N option is different because this is 11.31 cluster. But i have tested several times on v1.0VG with -N option, and it works fine.

Br
Patrik

[Unix System Engineers]

I am using MCSG A.11.18.00 with the latest patches along with version 2.1. The lock disk works.

T1905CA A.11.18.00 Serviceguard
PHSS_39047 1.0 Serviceguard A.11.18.00


Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/vglogs /dev/disk/disk67 up

--- Volume groups ---
VG Name /dev/vglogs
VG Write Access read/write
VG Status available, exclusive
Max LV 2047
Cur LV 3
Open LV 3
Max PV 2048
Cur PV 4
Act PV 4
Max PE per PV 655360
VGDA 8
PE Size (Mbytes) 16
Total PE 3468
Alloc PE 3194
Free PE 274
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 2.1
VG Max Size 10t
VG Max Extents 655360

[Carsten Krege]

SG A.11.18 patch PHSS_37602 or later is required to use LVM version 2.0 or 2.1 volume groups in Serviceguard, but without LVM Cluster lock support.

SG A.11.18 patch PHSS_38424 or later is required to use LVM version 2.0 or 2.1 volume group in Serviceguard, including with LVM cluster lock support.

Carsten