Cannot extend /tmp !

[Thierry Doppler]

Hi,

I have to extend the /tmp directory, but I can't umount it because always busy :

- I killed the bootp deamon with kill -9 an deactivate it in /etc/initd.conf with a # and started inetd -c

- then i do :
sapdev //#>init s
**** SYSCON CHANGED TO /dev/console ****

sapdev //#>umount /dev/vg00/lvol4
umount: cannot unmount /tmp : Device busy
umount: return error 1.

sapdev //#>fuser -cuk /tmp
/tmp:

- as you see no process is working on the /tmp directory. What can I do ?

Thank you for your help.

Thierry

[Tiziano Contorno _]

I suppose you do not have onlineJFS extensions, so you need to go to single user to be able to have /tmp unmounted.

shutdown

without arguments goes in single user, do a bdf and see if /tmp has been unmounted. Otherwise you have to reboot and interact with IPL typing

hpux -is

[Mohanasundaram_1]

Hi Thierry,

Please extend the /tmp directory in single-user mode. If you want to do it online without unmounting, then you need the OnlineJFS software.

If you do have this OnlineJFS then check man pages of fsadm for online filesystem extending.

With regards,
Mohan.

[Fabio Ettore]

Hi Thierry,

I suggest you to go on the single-user mode level (shutdown -ry 0 and stop the boot ---> bo pri ---> Interact with IPL? yes ---> hpux -is)

and then

lvextend -L /dev/vg00/
extendfs -F vxfs /dev/vg00/r

Once successfully init 3 and check the new /tmp size.

I think that should help you.

Best regards,
Fabio

[Arunvijai_4]

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1005254

-Arun

[DCE]

Unless you have online JFS, you cannot extend amounted file system.

You cannot unmount a file system is use, unfortunately /tmp is in use pretty much all of the time.

In order to extend it without online JFS, you will need to reboot the system into single user mode, mount /usr, /var and /opt and then extend /tmp

[Senthil Kumar .A_1]

Hi Doppler,

you can extend your tmp FS by not going into single user mode. You can acheive this by only a single reboot with a small modification sequence.

For details refer to the link provided in the previous response by Arunvijai.

Regards,
Senthil Kumar .A

[AshishJain_USA · Accepted solution]

Hi

Pls go to the single-user mode and then

# vgchange -a y /dev/vg00
# mount /usr
# lvextend -L /dev/vg00/
# extendfs -F vxfs /dev/vg00/r


You my then run

# mount /tmp

to check the new size


rgds...Ashish

[Frank de Vries]

Hi Thierry

You received most good answer, so i won't repeat them, however I would like to mention
for the future it would be handy to have
a utility like lsof installed.

This gives more detail about activity
and connections then fuser.

It could still be that you conclude to
have to go to single user mode, but at least
you know why (i.e. which application is
have file handles open etc..), or in
the best case you can stop the relevant
application or process and do the
umount and lvextend steps.

You can get lsof from hp open sourde kit
http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,4682,00.html

Hope this is handy

[Thierry Doppler]

Good Morning and Thanks very much to everyone.

I have done this steps :
- shutdown without arg to go to single-user mode
- lvextend
- umount /tmp
- extendfs
- mount

My problem was to switch to runlevel S because the system wait of a Return-Key (or perhaps any ey) after the message "Wait for transition to run-level S (allow 20 seconds)."
By waiting 20 sec. the system don't switch auf S-mode.

Regards
Thierry

[Kyris]

Thierry,

On my systems you need to hit spacebar on the heyboard in order to go to single user mode. Otherwise it will carry on !!

kyris

[Bill Hassell]

Unfortunately, init s/S has been broken for several years. Despite the man page stating that it will get you into single user mode, it doesn't. It leaves filesystems mounted, sometimes leaves network services running, etc. The same thing is true for shutdown 0. The man page states that without -r or -h, the system will transition to single user mode. But the result is similar to init s/S. This leaves /tmp (and others) still mounted with some processes still running. Both init s/S and shutdown 0 would be very useful if they worked as they bypass the lengthy hardware selftests.

So the only dependable method is to reboot, interrupt the boot process, and then use the ISL command: hpux -is

[Frank de Vries]

Thanks for that Bill !!
That explains some of my past probs with that. Nice one