From owner-freebsd-isp Sat Nov 9 18:16:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04639 for isp-outgoing; Sat, 9 Nov 1996 18:16:16 -0800 (PST) Received: from salsa.gv.ssi1.com (salsa.gv.ssi1.com [146.252.44.194]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04634 for ; Sat, 9 Nov 1996 18:16:12 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.ssi1.com (8.7.5/8.7.3) id SAA27584; Sat, 9 Nov 1996 18:16:01 -0800 (PST) From: Don Lewis Message-Id: <199611100216.SAA27584@salsa.gv.ssi1.com> Date: Sat, 9 Nov 1996 18:16:01 -0800 In-Reply-To: Howard Goldstein "Best mount options, tunefs for newsserver" (Nov 9, 4:59pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Howard Goldstein , freebsd-isp@freebsd.org Subject: Re: Best mount options, tunefs for newsserver Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Nov 9, 4:59pm, Howard Goldstein wrote: } Subject: Best mount options, tunefs for newsserver } For further performance improvements the tunefs (8) hints that a space } optimized fs costs a lot. My messages log shows /kernel keeps } changing the tuning of the news spool, although for the last two days } it's kept it on space optimized. Sometimes I have my doubts about its heuristics, but ... } I shouldn't really care much about } avoiding fragmentation on my frequently rm'd newsspool [should I...?] Yes you should if you get it close to full. I've had a badly spool totally run out of free blocks when df showed it still had about 5% free (including the minfree margin). The problem was that all the free space consisted of fragments, which are useless when you try to create a file that is at least block_size-fragsize+1 byte long. Once this happens, your news server grinds to a halt until expire frees up some blocks. --- Truck