have filesystem full but files aren't big enough to fill filesystem.
What other causes could have a filesystem filling up? filesystems are
/tmp and /usr

Thanks

Ken <ucstyle@hotmail.com> wrote:
> have filesystem full but files aren't big enough to fill filesystem.
> What other causes could have a filesystem filling up? filesystems are
> /tmp and /usr
>
You might have run out of inodes. This happens if you have tons
of very small files. See the 'df' command and look for 'Iused' columns.

John

"John Graat" <do-not-reply@graat.org> schrieb im Newsbeitrag
news:412caa07$0$559$e4fe514c@news.xs4all.nl...
> Ken <ucstyle@hotmail.com> wrote:
> > have filesystem full but files aren't big enough to fill filesystem.
> > What other causes could have a filesystem filling up? filesystems are
> > /tmp and /usr
> >
> You might have run out of inodes. This happens if you have tons
> of very small files. See the 'df' command and look for 'Iused' columns.
>
> John

Or sbdy deleted a file in the fs while a process still writes to it. Such a
deleted file would be invisible but nonetheless grow and use up space as
long as the process writes to it. Use fuser or lsof to find out which
processes access fs in question. Kill those old processes if possible.
Make sure your /tmp fs does not fill completely as otherwise your system
might behave strange ;-)

HTH,
Andreas

Sounds like someone cleaned up a file that was still in use/being
written to. Use the fuser command to find out if so:
fuser -d <file system>

ucstyle@hotmail.com (Ken) wrote in message news:<d526473a.0408250651.3fa8f947@posting.google. com>...
> have filesystem full but files aren't big enough to fill filesystem.
> What other causes could have a filesystem filling up? filesystems are
> /tmp and /usr
>
> Thanks



Use fuser to find processes that may have used up the space in the
file system by creating open I-nodes. (Not sure if I am describing the
scenario right but here goes...)

Syntax:

1) fuser -u /tmp
or
2) fuser -u /dev/hd3

Example:
You have a runaway process that created a large file in /tmp. Someone
deletes that file but it does not release the space because the
process is still active, locking the inode. When you find the process
and kill it, you unlock the space.

We had this problem happen with an AcuCOBOL unattended program in AIX
4.3 and have noticed it with a nohup'd Informix "ontape" command in
AIX 5.1 (even though you pass it the <CR> it needs to start the
backup).


Another issue could be a corrupted I-node map for /tmp or /usr. You
can try fsck for that issue.

Syntax: fsck /tmp

You may have to unmount the filesystem to correct corruption.