filesystem full - freebsd 5.3

[Oliver Fromme]

t c <namondo at gmail.com> wrote:
 > I've got the following error messages in dmesg.today, but there are lots
 > inodes (and free space) on that partition (/home):
 > 
 > pid 50371 (rateup), uid 0 inumber 1130885 on /home: filesystem full
 > pid 42486 (httpd), uid 80 inumber 1059960 on /home: filesystem full
 > pid 50614 (virtual), uid 1004 inumber 966735 on /home: filesystem full
 > (many times each row...)

Maybe the file system was really full at the time those
problems were logged.  Then some cronjob (e.g. logrotate
or whatever) cleaned up, and now you don't see any traces
of the problem anymore.

If you want to find out, you could monitor your free space
continously.  The easiest way to do that would probably be
a small shell script which appends `df -k /home` to a log
file in /var.  You can call the script every 5 minutes via
cron, for example.

Usually, when there are messages reporting that the file
system is full, it really _is_ full at that time.
In theory there could be some inconsistencies or other
damage of the filesystem, but in that case you should also
get other error messages.  If you want to be sure, umount
the file system and fsck it.  I bet there will be no
errors.

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"... there are two ways of constructing a software design:  One way
is to make it so simple that there are _obviously_ no deficiencies and
the other way is to make it so complicated that there are no _obvious_
deficiencies."        -- C.A.R. Hoare, ACM Turing Award Lecture, 1980