Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!enea!kth!draken!zap From: zap@nada.kth.se (Svante Lindahl) Newsgroups: comp.sys.pyramid Subject: Re: Need more inodes Message-ID: <566@draken.nada.kth.se> Date: 20 Sep 88 20:59:34 GMT References: <9836@tness7.UUCP> Reply-To: zap@front.se (Svante Lindahl) Organization: some Lines: 36 In article <9836@tness7.UUCP> mechjgh@tness7.UUCP (Greg Hackney ) writes: [ Problem with too few inodes on a large file system ] >/etc/newfs -v -n -i 512 /dev/iop/rpdisk00i 2363 > >produces > >/etc/mkfs /dev/iop/rpdisk00i 73872 18 27 16384 2048 16 10 60 512 >/dev/iop/rpdisk00i: 73872 sectors in 152 cylinders of 27 tracks, 18 sectors > 151.3Mb in 10 cyl groups (16 c/g, 15.93Mb/g, 2048 i/g) <---- >super-block backups (for fsck -b#) at: | > 16, 7816, 15616, 23416, 31216, 39016, 46816, 54616, 62416, 70216 | > | > always 2048 2048 inodes per cylinder group is the max. You can only use the -i option to decrease the number of inodes on your file system. What you can do, is decrease the number of cylinders in a cylinder group. This way you get more (and smaller) cylinder groups, but you still get 2048 inodes per cylinder group. Use the -c option for to mkfs/newfs for this. I am not sure if this has any bad side effects, but I haven't observed any on the file systems where I have done this. I also don't know if it is advisable to set the number of cylinders per group to a power of two, but since sixteen is a power of two I usually use -c 8 when I need to do this. Can anybody say for sure if this is reasonable way to solve the problem (Chris Torek, are you reading this group?), or give an alternative solution? It has worked for me, but no guarantees... Svante Lindahl Front Capital Systems zap@front.se