From owner-freebsd-stable@FreeBSD.ORG Tue Jan 9 17:37:24 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3464D16A403 for ; Tue, 9 Jan 2007 17:37:24 +0000 (UTC) (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 B652213C459 for ; Tue, 9 Jan 2007 17:37:23 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (cxinax@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l09HbGst026336; Tue, 9 Jan 2007 18:37:22 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l09HbGSZ026335; Tue, 9 Jan 2007 18:37:16 +0100 (CET) (envelope-from olli) Date: Tue, 9 Jan 2007 18:37:16 +0100 (CET) Message-Id: <200701091737.l09HbGSZ026335@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, ghelmer@palisadesys.com In-Reply-To: <45A29EAD.5050308@palisadesys.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 09 Jan 2007 18:37:22 +0100 (CET) Cc: Subject: Re: 6.x loosing record of free space after filesystem fills? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, ghelmer@palisadesys.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 17:37:24 -0000 Guy Helmer wrote: > I think we've finally found the cause of the problem - it wasn't just > occurring after heavy use, but was visible right after filesystem > creation! We regularly built new filesystems with "newfs -U -O 1 -b > 65536 -f 8192" Why are you using those blocksize and fragsize settings? (If you store large files, then you should at least also decrease the inode density, using the -i option.) Some time ago, Joe Greco wrote: > > the one unusual thing about the configuration is that the filesystem > > we are attempting to build on is a 136GB ccd across 4 scsi disks with > > the fsize=8192 and the bsize=65536 (it is mainly to be used for large > > data log files): > > FreeBSD doesn't support fsize/bsize so large. There are ongoing issues > within the filesystem code and VM code that will cause such filesystems > to break under heavy load. Matt Dillon also talked about this being less- > than-optimal for the VM system from some technical points of view. It has been a while, and I'm not sure if there are still problems with those non-standard fsize/bsize settings, but I would definitely try to avoid them for production use. 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. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie