Date: Mon, 19 Dec 2005 08:48:38 +0100 From: t c <namondo@gmail.com> To: freebsd-fs@freebsd.org Subject: filesystem full - freebsd 5.3 Message-ID: <18eab3b50512182348j72f95315x@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Oliver Fromme <olli@lurza.secnetix.de> wrote:
: t c < namondo@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 ful=
l
: > (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. The output from df doesn't
distinguish between the two types of available space. You can use
dumpfs(8) to do that.
Dworkin
This version seems more likely for me. Unfortunatly I can't read the output
of dumpfs. I tried to post, but my message was 'moderated', so I put that
output on this page:
http://dumpfs.szellem.org
ct
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18eab3b50512182348j72f95315x>