Re: filesystem full
From: Andreas Schulze (b79xan_at_gmx.de)
Date: 08/25/04
- Next message: sheadley: "How to handle Potential Problems with select()"
- Previous message: Pete's: "Re: AIX 5.2 Networking( nslookup & ping )"
- In reply to: John Graat: "Re: filesystem full"
- Next in thread: sumGirl: "Re: filesystem full"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 25 Aug 2004 17:23:03 +0200
"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
- Next message: sheadley: "How to handle Potential Problems with select()"
- Previous message: Pete's: "Re: AIX 5.2 Networking( nslookup & ping )"
- In reply to: John Graat: "Re: filesystem full"
- Next in thread: sumGirl: "Re: filesystem full"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
