Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jjb@zeus.cs.wayne.edu (Jon J. Brewster)
Newsgroups: comp.sys.sun
Subject: newfs: decreasing bytes/inode
Message-ID: <8902140259.AA04508@zeus.cs.wayne.edu>
Date: 22 Feb 89 19:43:22 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 8
Approved: Sun-Spots@rice.edu
Original-Date: Mon, 13 Feb 89 21:59:46 EST
X-Sun-Spots-Digest: Volume 7, Issue 166, message 5 of 15

Both newfs and mkfs have a parameter which is supposed to allow the user
to vary the number of inodes created in a filesystem.  However, it appears
that the parameter has no effect, judging from the output of the command
-- bytes/inode seems to be pegged at 2048.  Does anyone know if this is
true?  (I.e., is it perhaps only the informational message that's fixed at
2048?  Slim hope, I know.)  We run out of inodes at about 60% utilization
on this one filesystem (/usr/spool/news) and decreasing the bytes/inode
seems the only remedy.  Oh, we're running 4.0 on Sun-3's.