Operating System - HP-UX
1751736 Members
5900 Online
108781 Solutions
New Discussion юеВ

Re: addind space to a file system to a cluster

 
SOLVED
Go to solution
Waqar Razi
Regular Advisor

addind space to a file system to a cluster

One of the file systems in MC service guard environment is full. I have checked the volume group having logical volume for that file system. I has some free space available.

I added some space to the logical volume by using lvextend and then increased the file system by using fsadm.

My question is that do we need to do create map file and then copy it to other nodes in the cluster. In this case, we havent added any disk to the cluster. Just increased the logical volume and then the file system size by using the available space from VG.
3 REPLIES 3
Mark McDonald_2
Trusted Contributor
Solution

Re: addind space to a file system to a cluster

No new disk, so no map file required. That will work fine as it is.
sujit kumar singh
Honored Contributor

Re: addind space to a file system to a cluster

hi

Yes after lvextend, the extendfs to achieve that, but keep in view that lvextend requires the LV to unmounted.(that means that package should be ideally halted)


If the system on which the Packacge is running has onlineJFS installed then you absolutely do not require the package to be halted or the LV to be unmounted at all: do an lvextend followed by the fsadm.


Regards
sujit
Johnson Punniyalingam
Honored Contributor

Re: addind space to a file system to a cluster

Hi Razi,

>>My question is that do we need to do create map file and then copy it to other nodes in the cluster. In this case, we havent added any disk to the cluster<<<

No Need, Hence we are not adding disk we are only extending logical volume using lvextend File System with Online JFS.

Which Case , do we need to vexport and vgimport.?

if you are adding "new disk" You need to

Example:-
ServerA
========
vgexport -pvs -m vg03.map /dev/vg03

scp *.map userid@ServerB:/home/userid
(copying the map files to ServerB)

ServerB:-
=========
On the other node:
1. Export the VG
>>>vgexport /dev/vgxx

2. Recreate the directory
>>>>mkdir -p /dev/vgxx

3. Recreate the VG group file
>>>mknod /dev/vgxx/group c 64 0xMM0000
where MM is a unique identifier (ex 01 for vg01)

4. Preview the vgimport to check for any possible error
>>>>vgimport -pvs -m /dev/vgxx
where mapfile is the one copied from the first node

5. If no error, remove the preview mode
>>>>vgimport -vs -m /dev/vgxx

6. Activate in share mode
>>>>vgchange -a s /dev/vgxx

(Hope the above steps Clear's Your Question)

Thanks,
Johnson
Problems are common to all, but attitude makes the difference