File system full

[manoj_pu]

Hello

Actual utilization of filesystem is only 261 MB but bdf shows 100 % full.

This happens after running a java program (server - client socket program).This particular program doesn't store any data in the filesystem.

If I stop all applications then it releases the disk usage and bdf shows the actual disk usage (261 MB).


#bdf
/dev/vgfeed/lvopr 512000 512000 0 100% /home/opr
# du -sk /home/opr
510707 /home/opr

Please help me on this matter.

Rgds

Manoj

[Steven Sim Kok Leong]

Hi,

You have opened file(s) whereby the process holding on to these file(s) is still running but the file(s) have been removed.

Try to perform either fuser on lsof on the filesystem to identify which are the process(es) holding on to these files and terminate them.

# fuser -u /home/xyz
# lsof |grep /home/xyz

Hope this helps. Regards.

Steven Sim Kok Leong

[K.Vijayaragavan.]

Hi,

fuser -u /home/opr to see the list of process running on this folder and use ps -ef | grep to find out what is that process.

-Vijay

[Olivier LEGRAND]

Hi,

When the applications are running, you might have some big file. Just make a "fuser -u $file" to know which process are very glutton in space disk.

Regards

[manoj_pu]

Thanks for your reply.

I checked the files opened by fuser and lsof commands.

It shows only executables running from that filesystem opened by application. It is not opening any other files from that filesystem.

I am attaching the output of fuser and lsof.

If you have other suggestion on this please revert me.

Rgds

Manoj

[Heiner E. Lennackers]

Hi,

which filesystem are you using? vxfs or hfs?
if you are using hfs, check the minfree settings which tunefs.

Heiner

[Steven Gillard_2 · Accepted solution]

The fuser output you posted is indeed showing that some of the processes have files open on that filesystem. But the lsof output you provided is not helping because you restricted it to sockets only with the -i option. Try the lsof again, this time without -i and you will see a full list of the open files.

Its likely that one of the applications is creating/opening a file, then immediately unlinking its directory entry so that other applications cannot see it but the disk space remains in use. This is bad programming as it causes administrative headaches as you've seen.

To confirm this, run a tusc trace on the application while it is starting up - this will show the sequence of system calls and allow you to prove what the program is doing. Then ask the programmers to rectify this!

Regards,
Steve

[manoj_pu]

Hello all

Thanks to everybody..

I could traced out the log file opened by application.After deleting the file filesystem usage reduced to normal condition.


Regards

Manoj