Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: Fast Filesystem defaults
Message-ID: <1183@umcp-cs.UUCP>
Date: Sat, 10-Aug-85 17:40:42 EDT
Article-I.D.: umcp-cs.1183
Posted: Sat Aug 10 17:40:42 1985
Date-Received: Mon, 12-Aug-85 22:39:08 EDT
References: <597@brl-tgr.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 16

> If newfs were as ``friendly'' as the manual page claims,
>it would calculate all this junk from the average file size.

One question: where is it going to *get* the average file size?
(Specifying it with an option makes it essentially the same as -i.)

In general, one inode per 2K is way too much (try one per 4K for
a default), but you are a *lot* better off with too many inodes
than too few.  And (believe it or not) I managed to run out at
one/2K---I put /usr/spool/news on its own RK07 over at eneevax,
and it ran out of inodes.  I remade the file system with one inode
per 1K data....
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland