pvchange and lvchange for cluster node

[kholikt]

Hi,

I have a MC/SG two nodes cluster connected to VA7400. I need to do some lvchange and pvchange to the VG mounted in the primary node. Apart from this I need to do some vgreduce to remove non performance path and vgextend to import the new path. What else need to be done for the secondary node after changing all these in the primary node? Do I need do any vgimport?

[Sridhar Bhaskarla · Accepted solution]

Hi,

While 'lvchange' and 'pvchange' do not require any importing, changing the disk paths certainly do imagining that you have the similar new paths available on the secondary servers too.

Simply export the VGs on the secondary node. Preview export the VGs on the primary node and generate map files. If you are changing how the paths are accessed, then I suggest you use '-f' option. For ex.,

#ll /dev/vgxx/group
(note the minor number)
#vgexport -v -m /tmp/vgxx.map -f /tmp/vgxx.disks vgxx
Copy /tmp/vgxx.map and vgxx.disks onto the secondary node.
On secondary node
#mkdir /dev/vgxx
#mknod /dev/vgxx/group c 64 (from primary node)
#vi /tmp/vgxx.disks

Modify the disks according to the secondary node. You may have to change c## numbers.
#vgimport -v -m /tmp/vgxx.map -f /tmp/vgxx.disks vgxx

That should build your lvmtab exactly like the primary node. If you are not concerned about PV paths, then use '-s' option with both export and import.

-Sri

[Sridhar Bhaskarla]

Fat finger

#vgexport -v -m /tmp/vgxx.map -f /tmp/vgxx.disks vgxx

Add -p to the above

#vgexport -p -v -m /tmp/vgxx.map -f /tmp/vgxx.disks vgxx

-Sri