How to increase size of logical volume in shared volume group

[Emma_8]

Hi Sri

Thanks alot for looking through those steps for me, much appreciated.

Cheers
Emma

[Stuart Powell]

I didn't notice the instruction; it would be advisable to create a VG map after the changes are made, and copy the map to the other node in the ServiceGuard cluster. I do that after any LVM change that I make on a SG VG.

Stuart

[Emma_8]

Hi Stuart

Thanks for that. I'm not entirely sure of the commands to create the vg map and then copy this map over to the secondary node so would really appreciate if you could help me out with that.

Thanks
Emma

[Sridhar Bhaskarla]

Hi Emma,

Just to clarify it a bit. It doesn't hurt re-importing the VGs on the failover node but there is no need to.

You will need to reimport the volume groups on the failover node only if you

-Add/Remove the logical volumes
-Add/Remove the disks from the volume group

You don't need to do it to increase the size of a filesystem which is the case now. In case if you have to re-import the VGs, below is the procedure.

On the primary node (where the VG is active)

#vgexport -v -s -m /tmp/vgxx.map vgxx
#ll /dev/vgxx/group
(note the sixth field which is the minor number)
Copy /tmp/vgxx.map to the alternate node into /tmp directory

On the failover node

#vgexport vgxx
#mkdir /dev/vgxx
#mknod /dev/vgxx/group c 64 0x0?0000
(replace 0x0?0000 with the minor number you noted down on the primary node)
#vgimport -v -s -m /tmp/vgxx.map vgxx

You will need to do the above for all the VGs that are impacted with your change.

When you get a chance, try to failover the package onto the alternate node and see if everything comes up.

-Sri