From owner-freebsd-hackers Fri Oct 8 0:14:30 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 513A0157BB for ; Fri, 8 Oct 1999 00:14:21 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 6B1781925; Fri, 8 Oct 1999 09:14:02 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 6A31949CF; Fri, 8 Oct 1999 09:14:02 +0200 (CEST) Date: Fri, 8 Oct 1999 09:14:02 +0200 (CEST) From: Andrzej Bialecki To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Non-standard FFS parameters In-Reply-To: <199910080501.WAA98482@apollo.backplane.com> 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 On Thu, 7 Oct 1999, Matthew Dillon wrote: > :> > :> Try using a smaller block size, like 16K. If that doesn't work then just > :> stick with 8K I guess. The kernel's clustering code should still make it > :> reasonably efficient. > : > :Yeah, I guess that's the only way to do it on 3.x... But how can I speed > :up fsck then, since newfs will create millions of inodes I don't need > :which will cause fsck to run for ages... > : > :Andrzej Bialecki > > The problem should only be effected by the blocksize (-b) specification. > > Adjusting the bytes-per-inode (-i) specification in newfs should not > pose a problem. IOW now you say it's ok to use very high values of -i... ;-) 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