I am running AIX 3 4.

When I do a df I get:

Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 32768 10232 69% 1309 16% /
/dev/hd2 917504 86360 91% 19744 18% /usr
/dev/hd9var 131072 67712 49% 617 4% /var
/dev/hd3 65536 0 100% 72 1% /tmp
/dev/lv00 196608 35064 83% 899 4% /usr/welcome
/dev/lv02 32768 20568 38% 580 4% /usr/ob
/dev/lv01 1441792 656008 55% 4127 1% /home
/dev/lv04 425984 294376 31% 1319 1% /apps
/dev/lv03 1605632 238520 86% 1187 1% /u1
/dev/lv05 425984 272424 37% 9315 9% /u2
/dev/lv06 2031616 1188840 42% 751 1% /wk

This shows the /tmp is 100% used. I have looked in every /tmp directory I can find (by using 'find') and there are no big files filling up the space. How do I find the files that are filling up the space? I have already deleted all the 'core' and smit.log files. This happened a week ago and I cannot free up the space. Can anyone please help?

Thanks!

Steve

This will give you a full listing of directories/files in /tmp, in the order of the space they occupy. Then you can check out the individual files/directories and purge.

The only files I can find of any size are in the /tmp/vgdata/rootvg:

# cd vgdata
# ls
rootvg
# ls -l rootvg
total 112
-rw-r--r-- 1 root sys 336 Jul 08 23:32 hd2.map
-rw-r--r-- 1 root sys 24 Jul 08 23:32 hd3.map
-rw-r--r-- 1 root sys 12 Jul 08 23:32 hd4.map
-rw-r--r-- 1 root sys 12 Jul 08 23:31 hd5.map
-rw-r--r-- 1 root sys 144 Jul 08 23:31 hd6.map
-rw-r--r-- 1 root sys 12 Jul 08 23:31 hd8.map
-rw-r--r-- 1 root sys 48 Jul 08 23:32 hd9var.map
-rw-r--r-- 1 root sys 72 Jul 08 23:32 lv00.map
-rw-r--r-- 1 root sys 528 Jul 08 23:32 lv01.map
-rw-r--r-- 1 root sys 12 Jul 08 23:32 lv02.map
-rw-r--r-- 1 root sys 588 Jul 08 23:32 lv03.map
-rw-r--r-- 1 root sys 156 Jul 08 23:32 lv04.map
-rw-r--r-- 1 root sys 156 Jul 08 23:33 lv05.map
-rw-r--r-- 1 root sys 744 Jul 08 23:33 lv06.map

I'm not familier with .map files - can I safely delete these?

Steve

You need to use a program like fuser or lsof on /tmp. Files do not always have names. If a process has a file open, the space will not be released just because you unlink the only file name it has.

Yes, it is possible that a process is stuck in a loop and writing continuously to a log or a debug file. Can you check 'top' and see if any process is taking up an unusual amount of CPU %age?

There doesn't seem to be a 'top' command on this system.

Steve