Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!uwm.edu!uakari.primate.wisc.edu!cupcake!jwp
From: jwp@cupcake.sal.wisc.edu (Jeffrey W Percival)
Newsgroups: comp.unix.ultrix
Subject: Re: what are gnodes?
Keywords: gnodes inodes
Message-ID: <822@cupcake.sal.wisc.edu>
Date: 3 Feb 90 18:24:10 GMT
References: <2048@eric.mpr.ca> <2915@decuac.DEC.COM> <821@larry.sal.wisc.edu> <2049@eric.mpr.ca>
Reply-To: jwp@cupcake.UUCP (Jeffrey W Percival)
Organization: Space Astronomy Lab, Madison, WI
Lines: 22

In article <2049@eric.mpr.ca> parker@zaphod.mpr.ca (Ross Parker) writes:
>What I've called here the 'system' limit is implying that you're running
>out of in-core gnodes... i.e. you have more open files than the system
>can currently handle.
>
>The filesystem limit defines how many files can exist on the disk. Both
>limits may need to be adjusted. As the problem is happening in your 'news'
>partition, it's quite conceivable that your are running into the hard
>filesystem limit and will need to rebuild your disk (ugh!).

I've received a number of very helpful replies, of which this is an
example, and my thank-you's didn't all make it through the address
labyrinth...

I looked into the system limits and the filesystem limits, and it
appears my problem is indeed with the filesystem.  News articles tend
to be small, and use up fewer than the average number of blocks.  Hence
they deplete the reserve of inodes disproportionately.

Hi ho, hi ho, it's off to rebuild my filesystem I go...
-- 
Jeffrey W Percival (jwp@larry.sal.wisc.edu) (608)262-8686