From owner-freebsd-questions@FreeBSD.ORG Wed Nov 12 14:08:12 2008 Return-Path: Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 942751065678; Wed, 12 Nov 2008 14:08:12 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7AB918FC18; Wed, 12 Nov 2008 14:08:12 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from verizon.net ([63.28.162.53]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KA800D3M1TBXUM1@vms173003.mailsrvcs.net>; Wed, 12 Nov 2008 07:08:01 -0600 (CST) Date: Wed, 12 Nov 2008 08:15:11 -0500 From: Sergey Babkin Sender: root To: Varshavchick Alexander Message-id: <491AD6DF.24F8072F@verizon.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en, ru References: <20081112145105.T65116@comanche.metrocom.ru> X-Mailman-Approved-At: Wed, 12 Nov 2008 16:47:53 +0000 Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD 5.4 - filesystem full X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 14:08:12 -0000 Varshavchick Alexander wrote: > > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition > in question has about 15G free space and more than 10000000 free inodes. > Then all by itself the error dissapears, only to be repeated several hours > later. What can it be and where to look? The server runs mainly apache and > sendmail, nothing special. I vaguely remember that there was an issue with softupdates that didn't report blocks as free until the filesystem was synced, and with intense disk activity the filesystem was not syncing by itself often enough. -SB