Running out of disk space

[Daniel Wajsman]

Hi.
As I restarted my HP9000 Server messages telling that EVENT STORM ( 20 EVENTS IN 295 SEC.or similar)appeared,and I have run out of space in /var file system.I have trimmed every *.old and *.BAK file ,but the situation remains the same.I can??t even edit a small file.
What else can I do ?
Thanks

->> df -k
/home (/dev/vg00/lvol8 ) : 19853 total allocated Kb
10376 free allocated Kb
9477 used allocated Kb
47 % allocation used
/opt (/dev/vg00/lvol4 ) : 686990 total allocated Kb
448688 free allocated Kb
238302 used allocated Kb
34 % allocation used
/tmp (/dev/vg00/lvol5 ) : 384133 total allocated Kb
382042 free allocated Kb
2091 used allocated Kb
0 % allocation used
/usr (/dev/vg00/lvol6 ) : 648687 total allocated Kb
285083 free allocated Kb
363604 used allocated Kb
56 % allocation used
/var (/dev/vg00/lvol7 ) : 1536000 total allocated Kb
0 free allocated Kb
1536000 used allocated Kb
100 % allocation used
/stand (/dev/vg00/lvol1 ) : 75359 total allocated Kb
60698 free allocated Kb
14661 used allocated Kb
19 % allocation used
/ (/dev/vg00/lvol3 ) : 439145 total allocated Kb
357216 free allocated Kb
81929 used allocated Kb
18 % allocation used

[Jeff Schussele]

Hi Daniel,

First thing to do is determine what file(s) are filling /var - do this

du -akx /var | sort -nr | more

This will give you the files in /var sorted in descending order.
Then look at the biggest file(s) & what's filling them should stand out.
Then correct the situation & decrease the size of the file(s)

HTH,
Jeff

[Steve Steel]

Hi

SAM

Routine Tasks

System Log Files

trim the files.


Or

look for cores


Steve Steel

[Helen French]

Hi Daniel:

Some options:

1) If you have big files under /var/adm/crash and if you don't require any more, then delete those. These files are created by a system crash.

2) Check the bigger files in the file system with:

# find /var -xdev -size +10000 -exec ll {} \;

3) Check the newly created files in /var with:

# find /var -xdev -type f -mtime -2 -exec ll {} \;

4) Check the STM logs or other log files and trim them if don't require.

5) Increase the LV size by adding a disk.

HTH,
Shiju

[James R. Ferguson]

Hi:

In addtion to the above (excellent) diagnostic suggestions, you should run (if you are not already):

# cleanup -c 1 #...on 11.x

# cleanup #...on 10.20

Regards!

...JRF...

[Sachin Patel]

Hi Daniel,

#find /var -name core -print

Is you find any core file remove it.

# du -sk /var/*

then if /var/adm is bigger run
#du -sk /var/adm/* find out wich direcoty his the largest one. that way you can easily find out about largest file.

Sachin

[hpuxrox]

Daniel,

You could look into committing your patches.

cleanup -c 2

This will clean up some space in /var/adm/sw/save.

Also be sure to run a backup of this directory before doing so.

-Yates

[Victor_5]

1. remove core file
find /var -name core -exec ls {} \;

2. trim log file
SAM

3. find larger file
find /var -size +5000000c -print

4. go through large file one by one
du -sk |sort

5. check any application or database related temp files by using find command

Good luck!

[pap]

Hi,
Just for futurer reference, it is alsways better to keep /var/adm/sw as a seperate file system, that will prevent any disk space problems due to patches instalations....in future.

For making some room in //var you need to look at the following

1. remove core files
2. clean old patches. ( you can download patch for this from ITRC.)
3. look for bigger log files and remove or trim them.
4. In /var/adm/ directory there are cron and other directories. you can go in to those dirs and delete or trim log files. The log files for cronjobs are taking too much space if it has not been deleted for long time.

hope this helps.

-pap

[hpuxrox]

You may also wait to look into linking /var/mail/root to /dev/null if you never use root email and link /var/tmp to /tmp.