Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Serviceguard
cancel
Showing results for 
Search instead for 
Did you mean: 

Copying LVM configuration to failover node when filesystems are increased

Ravi-Joshi
Advisor

Copying LVM configuration to failover node when filesystems are increased

In a 2-node SG clustered environment, if I extend filesystem on one node, Is it necessary to do vgexport and vgimport

of LVM configuration to other node.

 

Normally when we add disks to VG on one node, we do vgexport and take mapfile. This mapfile is copied to node 2 and

vgimport is done there.

 

When I do not add disks to VG and I simply extend a lvol and increase the filesystem. Do I still need to do vgexport, take mapfile, move it to node 2 and then do vgimport.

 

Thank you,

 

Ravi Joshi

1 REPLY
Patrick Wallek
Honored Contributor

Re: Copying LVM configuration to failover node when filesystems are increased

>>if I extend filesystem on one node, Is it necessary to do vgexport and vgimport of LVM configuration to other node.

 

No, that is not necessary.  The information about the size of the LVs is stored and read from the LVM area on the disk.

 

>>Normally when we add disks to VG on one node, we do vgexport and take mapfile. This mapfile is copied to node 2 and vgimport is done there.

 

Correct.  That is only when adding disks.  This process is primarily done so that the /etc/lvmtab gets updated with the appropriate disk info so that HP-UX on the 2nd node knows which disks are part of each VG.