Extend FS on a HP-UX Cluster need help

[cheesytime]

no need to run the vgchange (step 1 and 2) then? thanks

[Mel Burslan]

Procedure looks okay to me but I am at the end of my workday. So, use your best judgement rather than someone else's who is between the chair and keyboard nonstop for almost 10 hours. :)

>>You forgot to add the stop pkg on your instructions :-)


sometime, preferably before a catastrophe hits, you need to *** take the cluster offline *** (not necessarily today if it is under management pressure)


I thought *** take the cluster offline *** included stopping the package(s) and everything ;-)

[cheesytime]

1) pvcreate /dev/rdsk/c8t2d5
2) vgextend /dev/vgdp /dev/dsk/c8t2d5
3) lvextend -L 26888 /dev/vgdp/lvomni <-- This makes the FS 26888MB right?
4) vgexport -v -p -s -m /tmp/vgdp-org.map /dev/vgdp
5) rcp /tmp/vgdp-new.map girdb:/tmp/


on node2

vgexport /dev/vgdp
mkdir /dev/vgdp
mknod /dev/vgdp/group c 64 0x110000
vgimport -v -s -m /tmp/vgdp-new.map /dev/vgdp


That would be it then, no vgchange or halting the pkg. Looks good to go?

[cheesytime]

I finally tuned it up my way, please let me know if this looks good:

1) cmhaltpkg -v pkgname
2) vgchange -c n /dev/vgdp
3) vgchange -a n /dev/vgdp
4) pvcreate /dev/rdsk/c8t2d5
5) vgextend /dev/vgdp /dev/dsk/c8t2d5
6) lvextend -L 26888 /dev/vgdp/lvomni <-- This makes the FS 26888MB right?
7) vgexport -v -p -s -m /tmp/vgdp-org.map /dev/vgdp
8) rcp /tmp/vgdp-new.map node2:/tmp/


ON NODE 2

vgexport /dev/vgdp
mkdir /dev/vgdp
mknod /dev/vgdp/group c 64 0x110000
vgimport -v -s -m /tmp/vgdp-new.map /dev/vgdp
cmrunpkg -v pkgname

[cheesytime]

Folks I need to get this done ASAP:

I finally tuned it up my way, please let me know if this looks good:

1) cmhaltpkg -v pkgname
2) vgchange -c n /dev/vgdp
3) vgchange -a n /dev/vgdp
4) pvcreate /dev/rdsk/c8t2d5
5) vgextend /dev/vgdp /dev/dsk/c8t2d5
6) lvextend -L 26888 /dev/vgdp/lvomni <-- This makes the FS 26888MB right?
7) vgexport -v -p -s -m /tmp/vgdp-org.map /dev/vgdp
8) rcp /tmp/vgdp-new.map node2:/tmp/


ON NODE 2

vgexport /dev/vgdp
mkdir /dev/vgdp
mknod /dev/vgdp/group c 64 0x110000
vgimport -v -s -m /tmp/vgdp-new.map /dev/vgdp
cmrunpkg -v pkgname

Looks good? THanks!

[kevin_m]

As mentioned above you don't need to take the package down to add a disk.

Changes:
removed requirements for cmhaltpkg and vgchange
added fsadm to dynamically increase the file system size
updated map file name to be consistent (unless you planned on renaming in another step)
removed requirement for cmrunpkg on second node

ON NODE 1
---------
pvcreate /dev/rdsk/c8t2d5
vgextend /dev/vgdp /dev/dsk/c8t2d5
lvextend -L 26888 /dev/vgdp/lvtest # yes, the new size will be 26888 MB
fsadm -F vxfs -v -b 26888M /test
vgexport -v -p -s -m /tmp/vgdp-org.map /dev/vgdp
rcp /tmp/vgdp-org.map node2:/tmp/

ON NODE 2
---------
vgexport /dev/vgdp
mkdir /dev/vgdp
mknod /dev/vgdp/group c 64 0x110000
vgimport -v -s -m /tmp/vgdp-org.map /dev/vgdp

I changed the logical volume and mount point to what you originally listed so adjust accordingly.
- Kevin

[Viktor Balogh]

looks good. but imho the 2nd step is unneeded, (the one with vgchange -c n)

if you have done a "vgchange -c n" then you must set the cluster flag back with "vgchange -c y" in order to start the package.