filesystem full - freebsd 5.3
olli at lurza.secnetix.de
Thu Dec 15 08:14:45 PST 2005
dlm-fb at weaselfish.com wrote:
> Oliver Fromme <olli at lurza.secnetix.de> wrote:
> : 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...)
> : [...]
> : 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.
> Perhaps more likely, he was trying to allocate full-size blocks, and
> the only things available were fragments.
I considered mentioning the fragments issue, too, but I
don't think it applies in this case. His file system is
22 Gbyte with 6 Gbyte free. I think it is very unlikely
that those 6 Gbyte are all fragments.
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.
"Documentation is like sex; when it's good, it's very, very good,
and when it's bad, it's better than nothing."
-- Dick Brandon
More information about the freebsd-fs