UNIX for Dummies Questions & Answers

What filesystem do think contains that file? Not sure? Do:
df -k /var/adm/wtmpx

I have already ran “cp /dev/null /var/adm/wtmpx” and it seems that everything is running smoothly along with the software that we are using. Below is the result after emptying wtmpx file:

# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 741263 518123 163839 76% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 727392 16 727376 1% /var/run
swap 728240 864 727376 1% /tmp
/dev/dsk/c0t0d0s7 36592677 913706 35313045 3% /export/home
/dev/dsk/c0t0d0s4 61407 9 55258 1% /var/dump
/dev/dsk/c0t0d0s3 493527 42 444133 1% /var/tmp


As you've noticed, the available used capacity in /dev/dsk/c0t0d0s0 directory decreased from 88% down to 76%. We gained about 12% more disk space now. I guess this would be enough to keep us going without the need of reformatting our hard disk anymore. Is there any more file/s that we need to empty to give us more additional disk space?

Everytime I open /dev/dsk/c0t0d0s0 directory, the only message I get is, “No open method defined for c0t0d0s0”. Obviously, it does not show what files are stored in it.

After running, “df -k /var/adm/wtmpx”, it came up with the following results:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 741263 518123 163839 76% /

In additing to this, all files in /var/adm directory resulted to the same output after running df -k.

That means you don't have a separate filesystem for /var or /var/adm (which is a very bad idea, IMHO) and hence the wtmp file is gobbling up your root fs.

To find out which files are using how much you can use the following command:

# du -ks /* | sort -rn

which would give3 you a sorted list of directories along which the number of Kilobytes used by the files in them. Go through the biggest ones and find out, if they contain files you could remove or shorten. For instance, if the output is like that:

123480 /bin
112749 /fubar
...

you can use the command

# du -ks /fubar/* | sort -rn

to investigate further what needs so much space in /fubar and so on.

I'd recommend you ask someone knowledgeable in *NIX to assist you, though, because it needs some system expertise to interpret the output of these commands.

bakunin