resizing or extending a logical volume within sam

[Andrew Kaplan]

Hi there --

I have a serviceguard cluster running on two hp-ux 11.11 systems. I have already gone through the motions of exporting and importing the newly resized volume group in question to both nodes. I now want to resize or extend the logical volumes within the volume group via SAM.

I started SAM, and checked under volume groups and logical volumes, but did not see a reference for resizing. Where and/or what else do I need to do in order to accomplish this task? Thanks.

[Pete Randall]

Disks and Filesystems > Logical Volumes (highlight the lvol) > Actions > Increase Size


Pete

[Rasheed Tamton]

Hi Andrew,

lvextend -L 20000 /dev/vg01/lv0l1
(extend the LV to 20000MB)

if you have online JFS, use fsadm
fsadm -b 20000M /export
(extend the /export mountpoint which is mounted with /dev/vg01/lvol1 to 20000M

if no online JFS:
umount /export (the mountpoint)
extendfs /dev/vg0l/rlvol1 (use raw name)

In SAM
From Disks and Filesystems/Logical Volumes, select the LV, Action Menu, Increase Size

Regards.

[Adam Winebaugh]

Andrew do yourself a favor and use the command line. Sam is useful I suppose but not for lvm, especially if SAN disks are involved. Use the below commands and save yourself some possible troubles.

A. lvextend â L 4000 /dev/vgxx/lvolx (increases the size of the lvol)

Note: the â L option is not used to specify the amount of space you want to â growâ the lvol by. It is used to specify TOTAL space needed after the lvextend. I used 4000 as a reminder that we are â growingâ the file system by 4 Gig. Also lvextend recognized sizes by Megâ s by default.)

B. fsadm â F vxfs â b 39000M /filesystem
(IF online JFS) if not use

umount and remount

[Andrew Kaplan]

Hi there --

I started running the lvextend and fsadm command on the logical volumes of the volume group. Altogether there are seven logical volumes that are to be resized.

The first logical volume was successfully resized, but the second one did not repeat the success of th first. The error message that appeared on-screen was the following:

vxfs fsadm: /dev/vg102/lvol3 is not the root inode of a vxfs filesystem.

What does this mean, and what do I need to do to resize this and the subsequent logical volumes?

[Adam Winebaugh]

Andrew,

Please post the entire message, include command given and output from command.

[Adam Winebaugh]

Andrew,

Please post the entire message, include command given and output from command.

I would think by the error given that it is not a mounted filesystem or is not a mount point.

[Adam Winebaugh]

for the fsadm portion the command should be

fsadm â F vxfs â b XXXXM/mountpoint

[Adam Winebaugh]

Sorry that posted funny


fsadm -F vxfs -b xxxxM /mountpoint

[Andrew Kaplan]

Hi there --

I discovered my mistake: When I ran the fsadm command, I put in the hardware path as opposed to the filesystem path. Sorry about that.

[Adam Winebaugh]

ok good so ya got it. Great.


Don't forget the points!!!!!