topic Re: extending /stand in Operating System - HP-UX

extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 13:53:06 GMT

need to extend /stand. i have enough disk to do so. need to figure out how.

my thought is to use make_tape_recovery (ignite).

Can i run a MR, in preview mode, edit the system_cfg file and resume that MR using the -r option? i forget how to resume. Any ideas?

then i would just recover the system using the tape..

will this work?

Re: extending /stand

James R. Ferguson — Tue, 07 Apr 2009 14:01:10 GMT

Hi Chris:

You can simply create your 'make_tape_recovery' tape; boot from it; and choose the "Advanced Installation" mode. In this mode you can resize all of the vg00 filesystems to your taste.

Regards!

...JRF...

Re: extending /stand

TTr — Tue, 07 Apr 2009 14:24:19 GMT

As mentioned, no need for -p, -r options.

One very useful option for the make_tape_recovery command in the "-I" (minus capital eye). It makes the WINSTALL installer stop at the "Advanced Installation" option without having to watch for that 10 second delay. Note this delay is within the installer, not the one for the default primary boot path.

Re: extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 14:26:54 GMT

thank you... points assigned.

Re: extending /stand

Jeff Schussele — Tue, 07 Apr 2009 16:17:05 GMT

Hi Chris,

I'll just toss my 2 cents in here.
Please be advised that if your vg00 extension impinges on *any* other VG then you're looking at archive restoral of that data.

Cheers,
Jeff

Re: extending /stand

Jeff Schussele — Tue, 07 Apr 2009 16:18:03 GMT

Sorry...meant /stand.

Re: extending /stand

Ganesan R — Tue, 07 Apr 2009 16:30:55 GMT

Hi Chris,

/stand is a static filesystem and will not grow normally. You can find if any unnecessary files resides on /stand before going for extend.

Re: extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 16:31:58 GMT

thats one of the issues. I don't know what can safely be removed.

Re: extending /stand

Jeff Schussele — Tue, 07 Apr 2009 16:35:15 GMT

Hi Chris,

Yes.. there are *only* 3 filesystems that cannot be modified without a total reboot/rebuild - stand, root & swap.
Else you can go hog-wild.

Rgds,m
Jeff

Re: extending /stand

Jeff Schussele — Tue, 07 Apr 2009 16:36:29 GMT

OK....before anybody snipes me - I *MEANT* Primary swap.

Re: extending /stand

Steven E. Protter — Tue, 07 Apr 2009 16:39:08 GMT

Shalom,

Yes it will work.

But lets cut to the question? Why do you need to extend /stand ?

All that is supposed to be kept there is the kernel and the files needed to built it.

I've not once in 11 years needed more space for that file system than the default.

Are you sure you don't have stuff that does not belong?

SEP

Re: extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 16:45:31 GMT

it's an older system running 11.23 v2 and need to install the latest patch set from HP. When trying to install, it says /stand will be out of room to build the kernel.

Re: extending /stand

Ganesan R — Tue, 07 Apr 2009 16:52:57 GMT

Hi,

What is the current size of /stand file system?

Use the below command to find which dir consumes more space.

#du -xk /stand |sort -nr |head -20

look into the top space consuming directories and try to clean if any unwanted files.

To list the top 10 large files in /stand filesystem,

# find /stand -xdev -type f -print | xargs ls -an | sort -nr -k 5 | head -10

Re: extending /stand

Jeff Schussele — Tue, 07 Apr 2009 16:55:42 GMT

Yep - I've seen that.
vmunix has become a pig as well as its support files.
Like I said - You'll need to do a make_recovery style backup & rebuild the root/boot disk & this time double the /stand size...Lord knows what HP will do to /stand *next* time.

Rgds,
Jeff

Re: extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 16:55:46 GMT

root@host1:/var/opt/ignite/recovery>du -xk /stand |sort -nr |head -20
239360 /stand
68624 /stand/crashconfig
64256 /stand/current
64256 /stand/backup
42136 /stand/last_install
5456 /stand/crashconfig/mod
552 /stand/current/mod
552 /stand/backup/mod
272 /stand/last_install/mod
240 /stand/crashconfig/krs
224 /stand/current/krs
224 /stand/backup/krs
80 /stand/last_install/krs
16 /stand/krs
8 /stand/current/bootfs/stand/current/mod
8 /stand/current/bootfs/stand/current
8 /stand/current/bootfs/stand
8 /stand/current/bootfs
8 /stand/crashconfig/bootfs/stand/current/mod
8 /stand/crashconfig/bootfs/stand/current

Re: extending /stand

TTr — Tue, 07 Apr 2009 17:09:53 GMT

Take a look at http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=&threadId=1290089 regarding /stand/crashconfig. You could get away with deleting its contents. But /stand is kind of small, if you can afford the downtime you should go through the make_recovery and re-ignite the server.

Re: extending /stand

Pete Randall — Tue, 07 Apr 2009 17:16:08 GMT

Chris,

It looks to me like you have 3 or 4 different versions of your kernel configurations saved via the kconfig command. Try running "kconfig -v" to see all the information about these versions. This may help you identify, and maybe eliminate one or more of them. Also do a man on kconfig for further info on the concept and use.

Pete

Re: extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 17:24:23 GMT

i have 3 versions. i think i could get rid of one of these

root@host1:/var/opt/ignite/recovery>kconfig -v
Configuration backup
Title Automatic Backup
Save Time Fri Jan 23 09:25:05 2009
Modify Time Fri Jan 23 09:25:05 2009
Kernel Path /stand/backup/vmunix

Configuration crashconfig
Title booted from 'import.config'
Save Time Tue May 15 06:30:15 2007
Modify Time Mon Jun 18 08:02:44 2007
Kernel Path /stand/crashconfig/vmunix

Configuration last_install
Title Created by last OS install
Save Time Wed Sep 8 11:38:43 2004
Modify Time Wed Sep 8 11:38:43 2004
Kernel Path /stand/last_install/vmunix

what do you suggest?

Re: extending /stand

Avinash20 — Tue, 07 Apr 2009 17:24:50 GMT

Please execute # kconfig to check is we have any backup kernels in /stand which can be deleted

Re: extending /stand

Chris Fadrowski — Tue, 07 Apr 2009 17:32:36 GMT

root@host1:/var/opt/ignite/recovery>kconfig
Configuration Title
backup Automatic Backup
crashconfig booted from 'import.config'
last_install Created by last OS install