Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!bellcore!faline!ulysses!mhuxt!ihnp4!gargoyle!jpusa1!news
From: news@jpusa1.UUCP (usenet)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Wierd 3b inode problem with news.
Message-ID: <548@jpusa1.UUCP>
Date: Fri, 6-Nov-87 12:14:57 EST
Article-I.D.: jpusa1.548
Posted: Fri Nov  6 12:14:57 1987
Date-Received: Thu, 12-Nov-87 03:31:00 EST
References: <283@paisano.UUCP>
Reply-To: stu@jpusa1.UUCP (Stu Heiss)
Followup-To: comp.sys.att
Organization: JPUSA - Chicago, IL
Lines: 17
Xref: mnetor comp.sys.att:1708 comp.unix.wizards:5405

Summary:

Expires:


In article <283@paisano.UUCP> demasi@paisano.UUCP (Michael C. De Masi) writes:
-I'm running usenet on a 3b2/400 Sys V r2.0.1 and I'm having
-a strange problem with the news file system (news is on its
-own file system to prevent it from interfering with other
-data)  Soon after I first installed news, I found that I
-had run out of inodes long before data blocks.

I've had similar behaviour when the disk partition fills up and you run out
of data blocks.  For some reason, when the data blocks become available again,
the inodes don't get returned to the freelist.  This is on a unisoft sys5 r0
box.  The cure, when it happens, is to fsck the disk.  Is this a generic bug in
sys5?  Anyway, try to avoid filling the partition and the problem will most
likely disappear.  I've hacked an rnews that checks for space on the disk
before spooling the incoming article.  It knows of a list of alternate
directories on other partitions to use when it gets dangerously low.
--
Stu Heiss {gargoyle,ihnp4}!jpusa1!stu