From owner-freebsd-hackers Tue Oct 5 13:58: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 462641564F for ; Tue, 5 Oct 1999 13:57:40 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 71A5D1925; Tue, 5 Oct 1999 22:56:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 70D1249DE for ; Tue, 5 Oct 1999 22:56:44 +0200 (CEST) Date: Tue, 5 Oct 1999 22:56:44 +0200 (CEST) From: Andrzej Bialecki To: freebsd-hackers@freebsd.org Subject: Non-standard FFS parameters Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The system in question (3.3-stable) needs to use a large FS (ca. 40GB). The defaults for such filesystem are ridiculous, given that it will hold at most couple of hundred big data files. So, my question is: * should I change the cpg (default 16) to some bigger value? * is it safe to run production system with non-standard block and fragment size (e.g. 32768 and 4096)? * what maximum value can I use for -i (bytes per inode) parmeter? I aalready tried 16mln ... * and finally, how th above choices affect the FS performance in my case? Thanks in advance for any insights! Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message