From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 07:48:41 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 28D3C16A41F for ; Mon, 19 Dec 2005 07:48:41 +0000 (GMT) (envelope-from namondo@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67D4C43D5A for ; Mon, 19 Dec 2005 07:48:40 +0000 (GMT) (envelope-from namondo@gmail.com) Received: by nproxy.gmail.com with SMTP id p48so364893nfa for ; Sun, 18 Dec 2005 23:48:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=li0a7MyB+9oNk6EhUJJsOgafkM3ugvzxr7q1yPZnEZUYbkYkjcHjcMasIu5cjsKu979d16pDkkkD0en/rmAlUtz6q/rkXLXdGLvuQz8uq4r1fwbyn0BF2qX9YvC8Vbq8p9ATJin0qEgOG+J+LmoS6+dtR7jbfegTXH6dhDMgPbk= Received: by 10.48.219.18 with SMTP id r18mr231695nfg; Sun, 18 Dec 2005 23:48:38 -0800 (PST) Received: by 10.48.213.13 with HTTP; Sun, 18 Dec 2005 23:48:38 -0800 (PST) Message-ID: <18eab3b50512182348j72f95315x@mail.gmail.com> Date: Mon, 19 Dec 2005 08:48:38 +0100 From: t c To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: filesystem full - freebsd 5.3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2005 07:48:41 -0000 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 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