Extend / root mount point in HP UX 11.23

[Chitta]

Hi All,
I am using HP UX 11.23,Suddenly i came to know my / mount point got filled 98%. How do i extend the / mount point with downtime? Early reply would be greatly appericiated.

Thanks and Regards,
Chitta

[unixguy_1]

Hi Chitta,

we can extend / file system.first you showuld check is there any unwanted files and core file sin your system,pls remove it and check the Volume is there any space.

then check the File system is it HFS r JFS.

then ypu can do to exten the file system.

use lvexten command to exten the file system.

Regards,
Unixguy.

[unixguy_1]

Hi Chitta,

Hold the make_recovery tape,just iam telling wehave to reinstall it.

and check is there any free space in VG00 volume group and use the below mentioned command.

lvextend -L -n

Regards,
Unixguy.

[john123]

Hi Chitta,

You can can not extend / filesystem very easily because root file system should be contiguous..

Before extending it just find out which files caused the file system to fill up..
Or consider to mount some other directories as a separate filesystem

Regards
john

[Wim Rombauts]

Chitta,

The first thing to do is to find possible logfiles, tracefiles or corefiles on your system and clean the root filesystem up.

What size is you root filesystem now ? That allows us to see if it is effectively too small, or that it contains just too many files that shouldn't be there.

Extending the root filesystem is not easy. On way is to create an ignite tape and ignite your system with it. This is een effective reinstallation of your server but all your configurationfiles are preserved. During this installation, you can configure a bigger root filesystem.

When you happen to have MirrorDisk/UX available, it is more easy. You can create a mirror of your current config, split it and then extend the root filesystem on the split mirror. After that, you can boot from the split mirror, drop the original volumes on your primary boot disk and mirror back again.

So let us know what your options are.

[unixguy_1]

Hi Chitta,

Better remove the core files and logfiles,that's the best thing.

becuase if you are extend the / file system,that time, Is there any problem the server will not boot,if it's a mirring boot disk,it's big problem,In mirror time they mintioned the quarom then only it will boot.
if the disk is 50% = > only the server will boot.

so remove the unwanted files.

Regards,
Unixguy.

[Chitta]

Hi All,
Thanks for quick response,
First of all the size of the mount point is too small nearly 200 MB and it was configured 5 years ago. Suddenly it got filled 98% am still investigating the root cause.And there is no such big log or trace files.Also i tried to boot with Recovery tape it falls error. Am not able to boot from Tape.

Error while restore from the tape, details is attached herewith.





* Loading configuration user interface, please wait...

ERROR: File: /usr/dt/lib/hpux32/libDtHelp.so.1 not found.

ERROR: File: /usr/dt/lib/hpux32/libDtSvc.so.1 not found.

ERROR: File: /usr/dt/lib/hpux32/libtt.so.1 not found.

ERROR: File: /usr/lib/hpux32/X11R6/libICE.so.1 not found.

ERROR: File: /usr/lib/hpux32/libICE.so.1 not found.

ERROR: File: /usr/lib/hpux32/X11R6/libSM.so.1 not found.

ERROR: File: /usr/lib/hpux32/libSM.so.1 not found.

ERROR: File: /usr/lib/hpux32/X11R6/libX11.so.1 not found.

ERROR: File: /usr/lib/hpux32/libX11.so.1 not found.

ERROR: File: /usr/lib/hpux32/X11R6/libXext.so.1 not found.

ERROR: File: /usr/lib/hpux32/libXext.so.1 not found.

ERROR: File: /usr/lib/hpux32/Motif2.1/libXm.so.1 not found.

ERROR: File: /usr/lib/hpux32/libXm.so.1 not found.

..............

ERROR: File: /usr/lib/hpux32/libXt.so.1 not found.

NOTE: loadfile: Process killed by signal: 9

loadfile command failed, retry? ([y]/n): y

/usr/lib/hpux32/dld.so: Unsatisfied data symbol '__libCsup_mutex_context' in lo.

NOTE: run_cmd: Process: 146 (loadfile): killed by signal: 9.

loadfile command failed, retry? ([y]/n):

Is there any version conflict?

Regs,
Chitta

[unixguy_1]

Yes it's version conflict?

how many capacity in / root?

becuase we can findout the unwanted files and all,OS will take some capacity in /.

Regards,
Unixguy.

[Ganesan R]

Hi Chitta,

First you should realise that 200MB is not sufficient for root filesystem. It is the minimum size to hold the root filesystem. This is because most of the people will allow the system to take the default values rather than modifying with enough space.

We cannot extend the root filesystem straight away like other filesystems because of contigious allocation policy.
There are unsupported ways to do it. But the preferred and HP supported way is to take ignite backup and restore with modified LV sizes.

For time being you can remove the old vg configuration files from /etc/lvmconf dir to free up some space.

#cd /etc/lvmconf
#ll *.old --> see how much space consumed
#rm *.old

also find if any big files or log files created on root and remove it.

#find / -xdev -name *log -print
#find / -xdev -size +5000 -print --> to find >5MB files

[Ganesan R]

Hi Chitta,

Forgot to mention. Here is the link to extend the filesystem without ignite. But note that this needs to be carried out with your own risk since it is not supported by HP.

http://www.symmetricwebsites.com/articles/HP-UX/hpuxDynamicallyExtendSlashAndOrStand.php

[OldSchool]

of course, the procedure noted in the link above requires online JFS....which nobody knows if he has....

[OldSchool]

how recent is the "make_tape_recovery"?

also, if it "suddenly" became full, take a look at the files in /dev. "tar"ing to a non-existent device will cause the backup to create a file there instead.

it is not the usual course to have to "extend" the root volume, as once the OS is in place, it should be fairly static. as you wouldn't normally be adding apps there, it shouldn't grow much, and certainly not "all of a sudden"

[Mark McDonald_2]

Use an ignite network or tape image, remember -x inc_entire=vg00.

Rebuild the box and interrupt the install and increase / file system.