/stand not enough when swinstall

[Hanry Zhou]

swinstall can't pass analysis phase, caused by not enough space on /stnd
/stand 51000 used 14000 available

I don't have anything to clean on /stand, and also don't want to extend the size of /stand for now, so under these two pre-conditions, the only choice I have is to move vmunix.prev to somewhere else. I know that will be risky if there is any thing wrong with vmunix when I reboot. However, it seems I dont have any other choices?

What I can do to minimize/avoid the risky?
In case of not being able to reboot the system, can I boot up the system from vmunix.prev located on another file system, say /usr?

Thanks,

[twang]

Hi,
Do you have ignited-ux installed?
To need to extend the /stand using ignite-ux tape.
Eg. use ignite-ux to create interactive tape:
# make_tape_recovery -AI
use this tape to boot the hpux box, it will prompt you to make changes to the vg00
I you case, I think extend the /stand is the best solution.

Best Regards
twang

[Patrick Wallek]

You are actually in pretty good shape. You can move your current vmunix.prev elsewhere and not worry.

When you install your patch(es) and the kernel gets recompiled, then your CURRENT vmunix will become vmunix.prev and you'll get a new vmunix kernel file.

So move the vmunix.prev that is currently there and don't worry about it.

[twang]

In addition, you may download ignite-ux via this link if you haven't installed it:
http://www.software.hp.com/products/IUX/download.html#pax1
To install ignite-ux:

- Copy the patch to the /tmp on you system
- Unshar the source:
# sh PHCO_xxxx

- To install:

# swinstall -x autoreboot=true -x match_target=true -s /tmp/PHCO_xxxx.depot

good luck!

[Sridhar Bhaskarla]

Hi,

I agree with Patrick. You are ok to move the existing vmunix.prev to another directory though that would not help you to boot.

Once the kernel build is successful, your existing kernel will be moved as vmunix.prev. So, you could always boot from it later in case if you get into trouble.

However, you will have to continue to do this excersize everytime you rebuild kernel because the size of your /stand would allow only two kernels (kernel that's being built and the current kernel).

You cannot boot from vmunix.prev from another filesystem.

-Sri

[Stuart Abramson_2]

The above answers are all correct.

However, how big is your /stand, and what is in it. here is mine, below. If you are in the 80 MB range, you should be fine.

As pointed out above, you can move/remove vmunix.prev and also, dlkm.vmunix.prev.

Sometimes old kernel copies get left in /stand/build. Look in there too.

Stuart

saroot@acshps05:/stand# ll
total 60154
-rw-r--r-- 1 root sys 19 Aug 9 2001 bootconf
drwxr-xr-x 3 root sys 2048 Jul 1 08:31 build
drwxr-xr-x 5 root sys 1024 Jul 1 08:41 dlkm
drwxr-xr-x 5 root sys 1024 Jul 1 08:14 dlkm.vmunix.prev
-rw-r--r-- 1 root sys 32820 Jul 12 11:01 ioconfig
-r--r--r-- 1 root sys 82 Aug 9 2001 kernrel
drwxr-xr-x 2 root root 8192 Aug 9 2001 lost+found
-rw------- 1 root root 12 Jul 1 08:39 rootconf
-rw-r--r-- 1 root sys 1301 Jul 1 08:29 system
drwxr-xr-x 2 root sys 1024 Jul 1 08:42 system.d
-r--r--r-- 1 root sys 1310 Jul 1 08:03 system.prev
-rwxr-xr-x 1 root sys 15496256 Jul 1 08:31 vmunix
-rwxr-xr-x 1 root sys 15228144 Jul 1 08:04 vmunix.prev

saroot@acshps05:/stand# bdf .
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol1 83733 32413 42946 43% /stand

saroot@acshps05:/stand# du -s * | sort -n
2 bootconf
2 kernrel
2 rootconf
4 system
4 system.prev
12 system.d
16 lost+found
66 ioconfig
1470 dlkm.vmunix.prev
1512 dlkm
1686 build
29760 vmunix.prev
30288 vmunix

[Stuart Abramson_2]

Well, I looked again. Your /stand is 51 MB, which is too small. Ignite...

[T. M. Louah]

The reason why IUX/make*recovery tape is the only supported way be cause /stand starts at the begining of the disk "/dev/Vg00/lvol1" its characteristique is strict/contigous ... the next lvol is vg00/lvol2 for swap, lvextend command will not find free PEs after the last PE in lvol1 to retain strict/continuous Flag.

By booting from IUX tape, you will have the ability to call the Advaced options under UserInterface to access the Filesystem filder for disk/lvol management.

Hope this clarifies the picture.

Cheers,
T??

[Sridhar Bhaskarla · Accepted solution]

HI Hanry,

Whenever you rebuild the kernel or install kernel filesets, it is a good practice to create a make_tape_recovery tape.

That will also give you a compromising solution to your problem. Move /stand/vmunix.prev to another filesystem. Let the kernel be built saving the current kernel as vmunix.prev. If neither of these kernels work after the reboot following an issue, you always have the choice of rebuilding your system with the make_tape_recovery tape and resize your /stand while doing so.

So, you do not necessarily resize your /stand now unless required. But it is required to create a make_tape_recovery tape whenever you touch your kernel.

-Sri

[Caesar_3]

Hello!

You can more the vmunix.prev also
in the build you probably have vmunix_test
that you can move.
After the recompilation of the kernel you
don't need this files.

Caesar