From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 12:20:19 2005 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3559D16A420 for ; Mon, 19 Dec 2005 12:20:19 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B59543D69 for ; Mon, 19 Dec 2005 12:20:16 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (rytytm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBJCKDch037707 for ; Mon, 19 Dec 2005 13:20:14 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBJCKDI8037706; Mon, 19 Dec 2005 13:20:13 +0100 (CET) (envelope-from olli) Date: Mon, 19 Dec 2005 13:20:13 +0100 (CET) Message-Id: <200512191220.jBJCKDI8037706@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <18eab3b50512182348j72f95315x@mail.gmail.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: filesystem full - freebsd 5.3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2005 12:20:19 -0000 [broken quoting recovered] t c wrote: > Dworking wrote: > > Oliver Fromme 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 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. 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. In the situation give, I think it is rather unlikely. > 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 You have plenty of blocks free. By the way, you have minfree set to 0%. That's usually not a good idea on general-purpose file systems for multiple users such as /home, and it degrades performance significantly. 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. "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn