Newsgroups: comp.unix.aix
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!theory.tn.cornell.edu!shore
From: shore@theory.tn.cornell.edu (Melinda Shore)
Subject: Re: Need more inodes
Message-ID: <1991Apr13.140929.19774@batcomputer.tn.cornell.edu>
Sender: news@batcomputer.tn.cornell.edu
Nntp-Posting-Host: theory.tn.cornell.edu
Organization: Cornell Theory Center
References: <1991Apr11.064139.16221@grasp1.univ-lyon1.fr> <6585@awdprime.UUCP> <MARC.91Apr12090853@marc.watson.ibm.com>
Date: Sat, 13 Apr 1991 14:09:29 GMT

In article <MARC.91Apr12090853@marc.watson.ibm.com> marc@watson.ibm.com (Marc Auslander) writes:
>I believe that the AIXV3 jfs uses the BSD inode scheme, in which I
>fixed percentage of the file system space is preallocated to inodes.
>When you grow the file system you get more inodes as well.  It
>appears, from looking at several file systems, that the constant is
>one inode for each 4k disk block in the file system.

Not so.  The BSD filesystem allows the administrator to specify how
many datablock bytes per inode.  On a Vax the default is 2048 bytes,
although your mileage may vary.  Also, you can't "grow" a filesystem,
as a general rule (you can if you have disk labels and you want to
extend the end, leaving the beginning cylinder where it is, and you
don't care about overwriting the filesystem that follows the one
you're growing).
-- 
                    Software longa, hardware brevis
Melinda Shore - Cornell Information Technologies - shore@theory.tn.cornell.edu
