From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 13:40:16 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 5A8B316A41F for ; Thu, 15 Dec 2005 13:40:16 +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 80B2C43D5D for ; Thu, 15 Dec 2005 13:40:15 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mbcncv@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFDeA5x057457 for ; Thu, 15 Dec 2005 14:40: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 jBFDeAYB057456; Thu, 15 Dec 2005 14:40:10 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 14:40:10 +0100 (CET) Message-Id: <200512151340.jBFDeAYB057456@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <18eab3b50512150212k4624d38er@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: Thu, 15 Dec 2005 13:40:16 -0000 t c 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