root file system full

[Mohamed K Ahmed]

Dear all,
I have an AS4100 running Tru64 UNIX V 4.0G that has root file system full at 102%.
I tried everything that is mentioned in the forums to delete unwanted files, but it is still full, I can't get it to decrese the space used.
Any thoughts...ideas...things I missed?

MO

[Michael Schulte zur Sur]

Hi,

please post:
showfdmn -k root_domain
du -kxs /
df -k

thanks,

Michael

[Mohamed K Ahmed]

The system is running on UFS not AdvFS
Attached is the outputs you wanted

MO

[Hein van den Heuvel]

Try this:

find / -mount -size +500k -exec ls -g {} \;

-mount

will find files on the same file system as the current starting path name so it will NOT go down /usr and so on.

-size +2000k

Start out looking at the somewhat bigger (2MB) files.
It may find a stray tar/dump or core file.
Perhaps a few too many vmunix versions?


- exec ls -f {} \;

show details for matching files.


Once you explained the biggies, take it a step down like:
find / -mount -size -2000k -size +500k

(any file on /rz8a between 1/2MB and 2MB)



hth,
Hein.

[Ravi_8]

Hi

rebooting the m/c once will release some space

[Michael Schulte zur Sur]

Hi,

1. Is there a reason, you use ufs?
2. / is quite small, you should increase it.
3. There is more than 50mb difference between du and df. Boot machine in single user mode and look for files in the mount points, which are now hidden by the mounted file systems.

greetings,

Michael

[Ralf Puchner]

reboot to single user mode to be sure no processes have opened files which are hidden if using "du".

delete old kernels lying around and use
du -k /. Have a closer look to the /tmp and /dev directory.

[Mohamed K Ahmed]

he output is attached, I don't think that I have multiple or so big files
I think maybe rebooting the machine will release some space, I will do this during the weekend, but why??

MO

[Michael Schulte zur Sur]

Mohamed,

when you delete a file, that is opened by a process, the space is not released. du is fooled by the absence of the file and does not count the space. Please boot the machine into single user mode and look into the mount directories for files.

hth,

Michael

[Hein van den Heuvel]

Michael wrote: "look for files in the mount points, which are now hidden by the mounted file systems."

Yeah, good point. I forgot to mention that.
Let's say you had /tmp with a few file in it.
No you create a new device and mount on /tmp.
The old files there will be 'hidden'.
But you do not APPEAR to have a mountpoint that qualifies for that. Still...

The 'big' file list shows nothing excessive really. It suggestes some moving/cleanup in /sys/binary.

but really, as others wrote, maybe / was just made too small.

next step would be
find -s /* -mount
or
find -s /*/* -mount

That will point you to the directories that have enough block to worry about.

Hein.