From owner-freebsd-hackers Tue Oct 5 16:15:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id A3AF5156A0 for ; Tue, 5 Oct 1999 16:15:28 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id SAA52090; Tue, 5 Oct 1999 18:13:12 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910052313.SAA52090@celery.dragondata.com> Subject: Re: Non-standard FFS parameters To: abial@webgiro.com (Andrzej Bialecki) Date: Tue, 5 Oct 1999 18:13:11 -0500 (CDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Oct 05, 1999 10:56:44 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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? > One thing that bit me before.... (from the newfs man page) BUGS The boot code of FreeBSD assumes that the file system that carries the kernel has blocks of 8 kilobytes and fragments of 1 kilobyte. You will not be able to boot from a file system that uses another size. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message