Xref: utzoo news.admin:6592 comp.unix.wizards:17695
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: news.admin,comp.unix.wizards
Subject: Re: Out of inodes.  SunOS4.0, gripe.
Message-ID: <2365@auspex.auspex.com>
Date: 16 Aug 89 19:07:36 GMT
References: <FLEE.89Aug4114513@shire.cs.psu.edu> <1989Aug6.074441.15954@utzoo.uucp> <1614@mcgill-vision.UUCP>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 13

>Indeed, there may not even *be* inodes...and when there is something
>like them, there may not be any limit on how many are available.

Well, the software from which C news gets its idea of "how many free
inodes" could conceivably cough up MAXLONG or something like that. 

>(Assumption: C news will work when its disk areas are NFS-remote.)

Unfortunately, in the case of the current NFS protocol, there's no way
to find out how many free files there are on a remote file system, even
if said file system supports the notion, which is why e.g.  a "df"
asking for the number of inodes gives you garbage over NFS.  The next
protocol revision should fix this.