Operating System - HP-UX
1848554 Members
6399 Online
104033 Solutions
New Discussion

Re: Root filesystem expansion

 
SOLVED
Go to solution
Mike Barron
Occasional Advisor

Root filesystem expansion

I have an HP 9000 T600. I need to expand my root filesystem "/". HP says I can't do it with a lvextend in single user mode, which makes sense being you can't unmount that filesystem. Any suggestiond out there will be highly appreciated.

Mike
9 REPLIES 9
James R. Ferguson
Acclaimed Contributor
Solution

Re: Root filesystem expansion

Mike:

A very interesting proposal by Tim Malnati was posed in this thread:

http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0xeee76c96588ad4118fef0090279cd0f9,00.html

...JRF...
CHRIS_ANORUO
Honored Contributor

Re: Root filesystem expansion

What you can do is:
1 Make a recovery boot tape with ignite.
2 Reinstall using the tape and interrupt the boot process to increase /(root)
3 Check for files that are filling up your root directory and delete them.Use this command (find / -xdev -size +1000000c -exec ll {} \;)
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Kofi ARTHIABAH
Honored Contributor

Re: Root filesystem expansion

Hi Mike:

Have you considered the ignite-ux alternative. If you create an ignite image and boot with it - you can interrupt it and setup your new / (as well as other fs sizes)

do a search on ignite in the forums for more information.

Good luck
nothing wrong with me that a few lines of code cannot fix!
Mike Barron
Occasional Advisor

Re: Root filesystem expansion

Thanks guys, I did consider The ignite_ux, I was just querying if there were any other methods of doing this. I appreciate all your help. I just freed up some space by deleting some file in the /stand directory. One being vmunix.prev. I now have the space needed hopefully.
Mike
James R. Ferguson
Acclaimed Contributor

Re: Root filesystem expansion

Mike:

BTW, /stand/vmunix.prev is the standard backup kernel. It's a good thing to have to boot from if /stand/vmunix ever gets corrupted! You might want to copy vmunix as vmunix.prev .

...JRF...
Mike Barron
Occasional Advisor

Re: Root filesystem expansion

I have it backed up on tape.. This would help if I ever needed to restore it back on the system right?
James R. Ferguson
Acclaimed Contributor

Re: Root filesystem expansion

Mike:

I don't believe you can create a bootable tape except with Ignite, of course. You should leave a copy of the kernel on disk in /stand. Then you can do:

ISL> hpux -is /stand/vmunix.prev

to boot to an alternate (previously good) kernel. See the System Administration Tasks manual for more details.

...JRF...
Mike Barron
Occasional Advisor

Re: Root filesystem expansion

Good point, what if I put it in another directory. Like /var, will that work?

Same concept, different location...

Alan Riggs
Honored Contributor

Re: Root filesystem expansion

The kernel needs to be in an hfs filesystem, unfortunately. Moving it to /var would not work if /var is jfs. Also, remember that your boot volume must be defined with lvlnboot, and the volumes must be defined as contiguous with no bad block relocation.

Bottom line: keep your kernel in /stand. Clear out other space if necessary. Rebuild the root VG if you cannot find enough space.

BTW -- alternative solution if you do not want to use ignite to rebuild VG00 is to boot to lvm maintenance mode, shrink primary swap, move extents for primary sway to the "back end" of where they were oiginally, extend /stand into the available extents.

make_recovry is a much "friendlier" solution.