Operating System - HP-UX
1833762 Members
2477 Online
110063 Solutions
New Discussion

Reclaiming space on / volume

 
SOLVED
Go to solution
Terry Barkoulas
Occasional Advisor

Reclaiming space on / volume

In trying to solve another problem I noticed that I have run out of disk space on the / volume on one of our servers. I am relatively new to Unix so this may something of an inane question, but can someone tell me if is safe to delete/move the core file that is at the root of the file system since it is taking up to 3MB on the / volume. Also is there a way to "tell" the system to dump core files to another volume
4 REPLIES 4
Geoff Wild
Honored Contributor

Re: Reclaiming space on / volume

Yes, you can delete/move it - you might want to see what caused it:

file /core

coredumps occur in the current directory that a process was running.

I don't think you can direct them elsewhere...

If space is tight, you may want to make_tape_recovery, then reboot, boot the tape, and resize your root disk.

http://docs.hp.com/hpux/onlinedocs/B2355-90837/B2355-90837.html

Rgds...Geoff

Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Jeff Schussele
Honored Contributor
Solution

Re: Reclaiming space on / volume

Hi Terry,

Here's a command to tell you what the largest files/dirs are in a filesystem.

du -akx / | sort -nr | more

largest will be at the top.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Terry Barkoulas
Occasional Advisor

Re: Reclaiming space on / volume

Thanks for the command Jeff. I found the output interesting to say the least. I am somewhat perplexed by it though since it seems that listing also includes files from another file system on another server. Is it possible to mount other file systems especially from other servers and make them part of the root filesystem.
Terry Barkoulas
Occasional Advisor

Re: Reclaiming space on / volume

Sorry about that guys, it seems a file from a restore that went awry caused that entry. Nonetheless thank you guys for your help.