Need extend root lvm using expert recovery shell

[Aungshuman Paul]

Hello,

Can anyone help me about extending the root LVM using the expert recovery shell after boot the system using internal OS DVD?

Currently I dont have any ignite backup.

Aungshu

[R.O. · Accepted solution]

Hi,

Look at this LVM recovery document:

http://www13.itrc.hp.com/service/cki/docDisplay.do?admit=109447627+1274095375111+28353475&docId=emr_na-c01037913-4&docLocale=en

And go to "Increasing root lv`s size, unofficial procedure"

Regards,

[Aungshuman Paul]

Thanks, Its a nice doc. I will let you know after update the ROOT LVM.

[rariasn]

Hi,

http://docs.hp.com/en/5992-6584/apes02.html

rgs,

[Bill Hassell]

Increasing the / directory is almost never required. A search of the HP-UX Forums will show you hundreds of posts requesting this operation but by simply fixing broken procedures. The most common problems with excessive / growth are:

1. Misspelling a backup device, thus filling /dev with a massive file.

2. Using / for general storage or worse, application storage.

3. Defective scripts that create thousands of small junk in /.

So, analyze the root directory and find out why / needs to be larger than 300-500 MB. Use this command:

du -kx / | sort -rn | head -20

The largest directories are at the top of the list. The two largest directories are /sbin and /etc. Here are examples of 4 versions of HP-UX simple installs:

11.00
/etc = 23 MB
/sbin = 11 MB

11.11
/etc = 63 MB
/sbin = 37 MB

11.23
/etc = 190 MB
/sbin = 98 MB

11.31 (PARISC)
/etc = 213 MB
/sbin = 113 MB

11.31 (Itanium)
/etc = 56 MB
/sbin = 170 MB

/dev is always less than 100 KB. IF larger, use this to find the mistakes:

find /dev -type f

No ordinary files are ever to be stored in /dev. If there are large files stored in /, they typically are there because root's HOME directory is /, the worst possible location. The HOME directory for root needs to be moved, along with all the "root-droppings" that are filling the / directory.

>> Currently I dont have any ignite backup.

Don't even think about resizing the root volume without an Ignite backup. All of the procedures to resize the root volume can seriously damage your system.

[Aungshuman Paul]

Thanks.Actually the system still in 1st phase of implementation. The SAP consultant want to increase the root from 1GB to 10 GB. Even though they dont give us any justification, why they need 10GB of root partition.

Most probably we will go reinstall the OS then restore all other VG configuration from backup.

But, Thanks all of you for nice post.

Aungshu

[atul2701]

Hi

IF your VG00 is mirrored u can do it online. Procedure attached.

But take the ignite backup before.

[R.O.]

"The SAP consultant want to increase the root from 1GB to 10 GB"

You should ask him why he wants to increase root FS in 9Gb. He must have its application in dedicated FS other than root.

Regards,

[Torsten.]

>> The SAP consultant want to increase the root from 1GB to 10 GB. Even though they dont give us any justification, why they need 10GB of root partition.


IMHO a totally wrong decision.


All data should be in another VG, not vg00.

Create a new VG on a new disk!

[Bill Hassell]

Your SAP consultant is not very familiar with HP-UX systems at all. Making the / mountpoint = 10 GB is simply insane, probably because the consultant is used to running tiny workstations where everything is stored in one big directory. There are so many things wrong with a giant partition, not the least of which will be your ability to create an Ignite backup. SAP is an application just like Oracle. The code must be installed in /opt (which might need to be increased to 2GB to 4GB) but the data belongs in another volume group, NEVER vg00 and certainly NEVER in the / directory.

If you are the system administrator, remember that you will be blamed for the future problems, long after the SAP consultant is gone and forgotten.

[VK2COT]

Hello Aungshu,

Do not waste your time on doing this.
Plus, you are breaking the best practices
for HP-UX. Root file system is not meant to
be a "dump wasteland" for every application
on tyhe planet (SAP included).

You are trying to help a person
who does not know what they are talking
about.

Get a better SAP consultant or ask
them for justification. Believe me,
there is NONE!

Cheers,

VK2COT

[chris huys_4]

Hi Paul,

Probably a sap consultant who is used to working on a solaris system, were giving the root "slice" "everything" that is not needed for the other "slices", of the rootdisk, is a common practice..

Greetz,
Chris

[Michal Kapalka (mikap)]

Hi Bill,

Making the / mountpoint = 10 GB is simply insane, probably because the consultant is used to running tiny workstations where everything is stored in one big directory.

- with all respect, yes of course you have to 99% right with the large or single /, but in my opinion, its depend on the Customer requrements, if you build for example some development system with SAP, and you have for example rx4640 with two disks, of course mirrored with LVM, because of SPOF, and actually nobody is able to define some FS size such a /, /opt, /usr ......, and them you need to make some standard SAP mount point structure, of course /oracle/....SAPID/.... dedicated in VG00s lvols, you don't have much choices.

its better to make a single FS / for the system, and of course separated FS ofor the SAP data and them after installation of SAP you can easy make Ignite and recover the system with dedicated system FS.

that's my personal opinion, saw it serveral times in the customers enviroments.

mikap

[John Guster]

What is the purpose of having 10GB of / file system? you should ask the SAP guy. SAP guy may just want some space to dump his application code temporary...

[Steven E. Protter]

Shalom,

The SAP consulting is cracked. I'd like to know what he's been smoking.

The root file system is not supposed to include any data files, not even from SAP. All files installed by SAP should be in mounted file systems, not root.

Please ignore the SAP consultant and tell him what Bill Hassell said.

SEP