Date: Tue, 28 Nov 95 10:53 WET From: uhclem%nemesis@fw.ast.com (Frank Durda IV) To: bugs@freebsd.org Subject: newfs gets you fewer inodes these days. Why? Message-ID: <m0tKTHh-00081GC@nemesis.lonestar.org>
next in thread | raw e-mail | index | archive | help
I just installed 2.1 on a system that had a secondary 2GB SCSI that had not been disklabeled and such since the 1.1.5.1 days. It ran 2.0.5 that way without incident but I thought it would be nice to get rid of all the moaning and complaining the 'slicer makes while booting. Ha! After installation, I discovered that the partitions no longer had sufficient inodes to hold the contents I needed to restore. The 1.1.5.1 filesystems were newfs'ed with default settings for inodes back in the 1.1.5.1 days, so THE DEFAULTS WERE USED. Promise. I was amazed at the time that I didn't have to tweak the values. As an example of what is happening, a 450Meg partition ended up with nearly 210K inodes on 1.1.5.1, but on 2.1.0, it got 61438, even less than what a SCO UNIX system would provide for the same size "divvy" (65520). 61438 inodes was I got even with that partition a bit bigger (now 504Meg). So, now I have to figure out how to make the partitions larger (including / and /usr which are both a bit on the small side Inode-wise) whilst still being able to take advantage of some of the installation automation. Does anybody know why the blocks-to-inodes default ratio calculation was changed because it certainly makes migrations more difficult. Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0tKTHh-00081GC>