need help extending /usr

[rmueller58]

All,

I figured I check here first as usual..

I need to extend /usr currently it resides on an internal disk on lv07, there is no more room on this particle PV or LV..
I need to add an LV I know.. can I extend the filesystem across multiple LV's ??

If so how can I do it without too much effort.. I'd appreciate any step by step process someone else may have to do this..

Thanks

Rex M - ESU#3

[malki_3]

Have you alreaday enough of free spece on rootvg vg00:
vgdisplay -v vg00
If yes you can make an Ignite backup(make_tape_recovery) and after you boot using this tape and you can extend your LV.

[rmueller58]

# vgdisplay -v vg00


--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 7
Open LV 7
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 2500
VGDA 4
PE Size (Mbytes) 8
Total PE 2168
Alloc PE 2166
Free PE 2
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

[rmueller58]

I have room on other vg's but not on vg00..

--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8683
VGDA 2
PE Size (Mbytes) 8
Total PE 4340
Alloc PE 1925
Free PE 2415
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

# vgdisplay -v vg02
--- Volume groups ---
VG Name /dev/vg02
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8683
VGDA 2
PE Size (Mbytes) 8
Total PE 4340
Alloc PE 1508
Free PE 2832
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0


--- Volume groups ---
VG Name /dev/vg04
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 16
Open LV 14
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8683
VGDA 2
PE Size (Mbytes) 8
Total PE 4340
Alloc PE 2476
Free PE 1864
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

[Bryan D. Quinn · Accepted solution]

Hello,

You can not extend your file system across multiple LV's. You will need to extend the LV that /usr is mount on, which typically is /vg00/lvol7. But, if you do not have enough available extents in vg00, then you will need to add a disk to the volume group. You do not want /usr to be mounted on an LV that belongs to a volume group other than vg00. That is bad juju! I would recommend either adding a disk to vg00 or looking for unused LV's in vg00 that can be canned and those extents freed up in vg00. Then when you have enough free extents you can do an Ignite on the box and adjust the size of your /usr filesystem. Using Ignite will ensure that you have contiguous extents for /usr.

Hope this helps!
-Bryan

[rmueller58]

Ok

looks like I'm toast without redoing vg00.. Darn.. I thought I might be able to span a VG across disks.. Ok.. Thanks guys..

[Robert-Jan Goossens]

Hi Rex,

Three options.

cleanup inside /usr filesystem (if it is possible)
# du -ks /usr | sort -rn | more

add a disk to VG00.

move a filesystem from VG00 to VGXX, or a part from /usr to a new filesystem. example could be /usr/local
# bdf | grep vg00


Regards,
Robert-Jan

[Bryan D. Quinn]

Hello Rex,

What do you mean span a vg across disks? You can have multiple disks in a vg, but it has to be the entire disk. You can't have a physical volume that has x number of extents belonging to vg00 and y number of extents belonging to vg01. That will not work.

And as far as moving /usr out of vg00, that is possible just not recommended.

Another curiosity question here, how many disks do you currently have in vg00 and how big are they?

-Bryan

[rmueller58]

Bryan..
Two Seagate drives,, I believe the 9gb standards.. I have a RAID with 16 18 gb drives in a subsystem.. I will see if I can allocate an additional disk to vg00..

--- Physical volumes ---
PV Name /dev/dsk/c1t6d0
PV Status available
Total PE 1084
Free PE 1
Autoswitch On

PV Name /dev/dsk/c2t6d0
PV Status available
Total PE 1084
Free PE 1
Autoswitch On

[Bryan D. Quinn]

Hello Rex,

Robert-Jan brings up a good point in his #3 scenario, mounting a portion of /usr to another LV. We are an SAP shop and under /usr we have a /usr/sap directory which is required to be considerably larger than /usr roughly 7Gb, so we have it mounted to /vg01/lvol4. That way we don't take up so many extents in vg00.

-Bryan

[rmueller58]

Our main disk hog is /usr/informix (not the databases) and I just added perl 5.8.2 it increased disk use by another 5% from 93% before.. I hate seeing any file system over 90% prefer 70% as a baseline for increasing.. Checked all the logs and tmp files and cleaned up what I could..
May have to change logging file system within informix.. This would probably take care of it..

394285 /usr/informix/logs

[Bryan D. Quinn]

Hello again Rex,

Are those disks mirrored? Even so, you should have plenty of room with 9Gb to house your OS. What is using up all the extents in vg00? Do you have an application that is residing there? If so, I would consider breaking that out of vg00 and mounting them on new LV's in a different vg, like Robert-Jan was suggesting.

-Bryan

[rmueller58]

Bryan,

they are mirrored,

I did find a stats.log in my
/usr/informix/logs

If there are any Informix propellers in the reading audience can I rotate this pig, off to another filesystem?????

[Bryan D. Quinn]

Hello Rex,

I would look into moving /usr/informix to it's own LV. So that you would have /usr mounted on /vg00/lvol7 and /usr/informix mounted on something like /vgXX/lvolX. That way you take away the stress of having /usr/informix in vg00.

-Bryan

[rmueller58]

Bryan,

Thats my thought too now.... Looks like a weekend of work.. Thanks again all..

[Robert-Jan Goossens]

Hi Rex,

http://www.prstech.com/src/rotate_informix_logs.sh.txt

Regards and a good weekend (:-)

Robert-Jan

[rmueller58]

Thanks.. Robert and Bryan.. Move the log file in question and file system is back to reasonable level.. (77%)..

I will leave feedback.. Thanks!!