Serviceguard Extend a Filesystem

[Richard Ace]

I need to extend a filesystem on a Serviceguard cluster. I do not harldy know much about serviceguard and have heard that there are dangers of blowing a disk away that is in use else where on the cluster if you pvcreate it on one server and could be in use on the other server. I have heard about making the vg exclusive. and thought that something may need to be done on the failover node to let go of filesystem so it can be extended on the primary node. Is there a simple proceedure to all this. Can anyone shine some light on this, or point me in the right direction. Thanks in advance for you help. oh all have 10 points too.

INFO BELOW

uname -a
HP-UX nears B.11.11 U 9000/800 605389312 unlimited-user license
nears (/home/root) # model
9000/800/N4000-55
nears (/home/root) # bdf /dbdata
Filesystem kbytes used avail %used Mounted on
/dev/vgars/lvol29 30720000 27262696 3405416 89% /dbdata



nears (/home/root) # cmviewcl -v

CLUSTER STATUS
bears up

NODE STATUS STATE
lbears up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/1/0/0 lan2
STANDBY up 0/0/0/0 lan0
PRIMARY up 0/3/0/0 lan3
STANDBY up 0/9/0/0 lan1

PACKAGE STATUS STATE AUTO_RUN NODE
RPTEARS up running disabled lbears

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 RPTEARS

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled lbears (current)

NODE STATUS STATE
nears up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/0/0/0 lan0
PRIMARY up 0/4/0/0 lan1
STANDBY up 1/12/0/0 lan3
STANDBY up 0/5/0/0 lan2

PACKAGE STATUS STATE AUTO_RUN NODE
EARS up running enabled nears

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 EARS

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled nears (current)
Alternate up enabled lbears

[Masud Parvez · Accepted solution]

Send this output

vgdisplay -v /dev/vgars

If you have space into this VG then it is very easy.

Do you have OnlineJFS installed into your system?

[Fabio Ettore]

Hi Richard,

I think you can do that with no stop.

If only you have to extend the filesystem size then on the node with package/VG active:

lvextend -L /dev//

fsadm -F vxfs -b M /
(this assumes you have OnlineJFS)

Instead if you have to add a PV before of extending lvol/filesystem then on the node with package/VG active:

1- vgextend /dev/ /dev/dsk/cXtXdX

2- and then lvextend/fsadm as above;

3- vgexport -p from this node and vgimport onto the secondary one.

HTH.

Best regards,
Fabio

[Richard Ace]

swlist -l product |grep -i jfs
JFS B.11.11 The Base VxFS File System
PHKL_24026 1.0 JFS Filesystem swap corruption
PHKL_28512 1.0 Fix for POSIX_AIO in JFS3.3
PHKL_29115 1.0 JFS Direct I/O cumulative patch
PHKL_30366 1.0 JFS3.3;ACL patch
PHKL_34805 1.0 JFS3.3 patch; mmap

[Richard Ace]

There is space

vgdisplay -v /dev/vgars
--- Volume groups ---
VG Name /dev/vgars
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 13
Open LV 10
Max PV 16
Cur PV 10
Act PV 10
Max PE per PV 8683
VGDA 20
PE Size (Mbytes) 2
Total PE 86810
Alloc PE 74144
Free PE 12666
Total PVG 2
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vgars/ars
LV Status available/syncd
LV Size (Mbytes) 5000
Current LE 2500
Allocated PE 5000
Used PV 4

LV Name /dev/vgars/oracle
LV Status available/syncd
LV Size (Mbytes) 3000
Current LE 1500
Allocated PE 3000
Used PV 2

LV Name /dev/vgars/data1
LV Status available/syncd
LV Size (Mbytes) 4000
Current LE 2000
Allocated PE 4000
Used PV 8

LV Name /dev/vgars/data4
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 1000
Allocated PE 2000
Used PV 2

LV Name /dev/vgars/ars452
LV Status available/syncd
LV Size (Mbytes) 1000
Current LE 500
Allocated PE 1000
Used PV 2

LV Name /dev/vgars/artmp
LV Status available/syncd
LV Size (Mbytes) 6000
Current LE 3000
Allocated PE 6000
Used PV 8

LV Name /dev/vgars/lvol26
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 1000
Allocated PE 2000
Used PV 2

LV Name /dev/vgars/lvol27
LV Status available/syncd
LV Size (Mbytes) 8096
Current LE 4048
Allocated PE 8096
Used PV 3

LV Name /dev/vgars/lvol29
LV Status available/syncd
LV Size (Mbytes) 30000
Current LE 15000
Allocated PE 30000
Used PV 8

LV Name /dev/vgars/lvol30
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 4000
Allocated PE 8000
Used PV 3


--- Physical volumes ---
PV Name /dev/dsk/c3t0d0
PV Name /dev/dsk/c7t0d0 Alternate Link
PV Status available
Total PE 8681
Free PE 667
Autoswitch On

PV Name /dev/dsk/c3t1d0
PV Name /dev/dsk/c7t1d0 Alternate Link
PV Status available
Total PE 8681
Free PE 861
Autoswitch On

PV Name /dev/dsk/c3t2d0
PV Name /dev/dsk/c7t2d0 Alternate Link
PV Status available
Total PE 8681
Free PE 2645
Autoswitch On

PV Name /dev/dsk/c3t3d0
PV Name /dev/dsk/c7t3d0 Alternate Link
PV Status available
Total PE 8681
Free PE 2644
Autoswitch On

PV Name /dev/dsk/c3t13d0
PV Name /dev/dsk/c7t13d0 Alternate Link
PV Status available
Total PE 8681
Free PE 1540
Autoswitch On

PV Name /dev/dsk/c4t0d0
PV Name /dev/dsk/c6t0d0 Alternate Link
PV Status available
Total PE 8681
Free PE 0
Autoswitch On

PV Name /dev/dsk/c4t1d0
PV Name /dev/dsk/c6t1d0 Alternate Link
PV Status available
Total PE 8681
Free PE 0
Autoswitch On

PV Name /dev/dsk/c4t2d0
PV Name /dev/dsk/c6t2d0 Alternate Link
PV Status available
Total PE 8681
Free PE 0
Autoswitch On

PV Name /dev/dsk/c4t3d0
PV Name /dev/dsk/c6t3d0 Alternate Link
PV Status available
Total PE 8681
Free PE 0
Autoswitch On

PV Name /dev/dsk/c4t13d0
PV Name /dev/dsk/c6t13d0 Alternate Link
PV Status available
Total PE 8681
Free PE 4309
Autoswitch On


--- Physical volume groups ---
PVG Name grp1
PV Name /dev/dsk/c7t0d0
PV Name /dev/dsk/c3t1d0
PV Name /dev/dsk/c7t2d0
PV Name /dev/dsk/c3t3d0
PV Name /dev/dsk/c7t13d0

PVG Name grp2
PV Name /dev/dsk/c6t0d0
PV Name /dev/dsk/c4t1d0
PV Name /dev/dsk/c6t2d0
PV Name /dev/dsk/c4t3d0
PV Name /dev/dsk/c6t13d0

[Fabio Ettore]

Hi Richard,

so you can extend filesystem without adding a new PV (in that case you should add two toghether to respect the PVG policy).
But you have to umount the filesystem to extend it:

lvxtend -L /dev/vgars/
umount /
extendfs -F vxfs /dev/vgars/r
mount /dev/vgars/ /

Umount filesystem means stopping applications that insist on.

Best regards,
Fabio

[Deepak Kr]

Hi Richard,

Yes, you can do it

steps:

#bdf /dbdata

/dev/vgars/lvol29 30720000 27262696 3405416 89% /dbdata


All you need is to have free space available in Volume group

vgdisplay vg_name |egrep -i "Free|PE"
Then you can calculate free size
free size in MB =Free PE * PE size

Now check if you have Online JFS installed

swlist |grep -i Online

If yes, run

on the node where file system mounted

lvextend -L new size LV_name
fsadm -b /filesystem mount point



or

If no Online JFS ====Downtime required

Halt the package on the node that using /dbdata

cmhaltpkg -v

This will unmount and remove access to /dbdata

mount vgars in exclusive mode on one of node and extend /dbdata as required

vgdisplay -a e /dev/vgars

lvdisplay /dev/vgars/lvol29

lvextend and then extendfs commands

lvdisplay /dev/vgars/lvol29

Once done

vgcfgbackup vgname

vgdisplay -a n /dev/vgars


start package cmrunpkg -v package name
enable switching cmmodpkg -e


Hope this will solve your query!!

[Deepak Kr]

You can check OnlineJFS like:
swlist |grep -i online
B3929DA B.11.23.0512 HP OnLineJFS (Server)

[Deepak Kr]

sorry for typo:

One correction:

vgchange -a e vgname
vgchange -a n vgname

[Masud Parvez]

You don't have OnlineJFS so you need to stop your cluster before doing this otherwise your cluster will fail if you unmount your file system.

Better shudown your cluster and do this work after activating you VG. when you have done then inactive that VG and startup your cluster.

[Deepak Kr]

Only package shut will work.

[Aashique]

Hi,

Here are the steps:

1# halt the cluster. ( cmhaltpkg -v pkg_name)
2# vgchange -c n /dev/vgars
vgchange -a n /dev/vgars
3# vgexport -v -p -s -m /tmp/vgars-org.map /dev/vgars (take the vg backup)
4# lvextend -L newsize /dev/vgars/lvol29 (newsize in MB)
5# vgexport -v -p -s -m /tmp/vgars-new.map /dev/vgars
6# rcp /tmp/vgars-new.map 2nd-node:/tmp/

7# rlogin 2nd-node
8# in 2nd-node vgexport /dev/vgars
9# mkdir /dev/vgars
10# mknod /dev/vgars/group c 64 0x110000(check the available minor number)
11# vgchange -a n /dev/vgars
12# vgimport -v -s -m /tmp/vgars-new.map /dev/vgars

13# start the cluster in first node:
cmrunpkg -v pkg_name


Thanks & Regards
Aashique

[Aashique]

Hi,
i Missed one point--
after lvextend use extendfs

Thanks.

[Richard Ace]

your preceedure differs from Kumar as he said

to

vgchange -a e vgname
vgchange -a n vgname

thanks rich

[Aashique]

Hi,
vgchange -c n
-->
Control the membership of volume groups in a
high availability cluster.
here n means: Remove each specified volume group from membership in the high availability cluster. The high availability software does not need to be running.

vgchange -a n
-->
Deactivate each specified volume group and its associated logical volumes. You must close the logical volumes prior to executing
this option. For example, if the logical volume contains a file system, the file system must be unmounted.


Thanks.

[sri_sri137]

I have free space in VG. And I want to extend the file system in primary node which is currently active. This is 2node service guard cluster and onLineJFS also there. so apart from the lvextend and fsadm commands can we need to take care any other cluster related files or map files in both the nodes?

Can we export the map file on primary and import the same map file in alternate node?

[RAJD1]

if you are not adding additional disk to the VG , map file export not needed.

If you have free space in the VG, you just need to extend it using  lvextend and fsadm command , it is online.  Cheers.