Xref: utzoo news.software.b:1672 news.admin:3707 news.sysadmin:1079 comp.unix.wizards:11709 comp.bugs.sys5:617
Newsgroups: news.software.b,news.admin,news.sysadmin,comp.unix.wizards,comp.bugs.sys5
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: Alzheimer's Syndrome (a.k.a. disappearing inodes) analysis & test
Message-ID: <1988Oct14.162501.854@utzoo.uucp>
Organization: U of Toronto Zoology
References: <1384@cooper.cooper.EDU> <308@stca77.stc.oz>
Date: Fri, 14 Oct 88 16:25:01 GMT

In article <308@stca77.stc.oz> peter@stca77.stc.oz (Peter Jeremy) writes:
>...on a
>clean file system the free inode list should be sorted, and therefore
>inodes should be allocated in inode order).

Well, do remember that there's no such thing as a "free inode list" with
all the free inodes of the filesystem on it.  What there is, is an in-core
list of up to circa 100 free inodes.  That list is only a hint to improve
performance; it's the inode itself that records whether it is allocated
or not.  If the in-core list fills up, Unix just throws away the extra
hints.  If the in-core list becomes empty, Unix searches the filesystem
for more free inodes to refill it.  "Searches" means just what you think
it does:  sequential search through the inodes looking for empties.  In
modern Unixes an attempt is made to start the search from a different
point each time, to avoid long delays.  There is plenty of room for bugs
and odd behavior in this scheme.

(NB:  SysV and BSD have each added their own wrinkles which change some of
the details of the above.)
-- 
The meek can have the Earth;    |    Henry Spencer at U of Toronto Zoology
the rest of us have other plans.|uunet!attcan!utzoo!henry henry@zoo.toronto.edu