Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!ucbcad!ucbvax!sdcsvax!nosc!humu!uhmanoa!aloha1!islenet!richard
From: richard@islenet.UUCP (Richard Foulk)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Wierd 3b inode problem with news.
Message-ID: <3646@islenet.UUCP>
Date: Tue, 17-Nov-87 21:40:10 EST
Article-I.D.: islenet.3646
Posted: Tue Nov 17 21:40:10 1987
Date-Received: Sat, 21-Nov-87 11:06:44 EST
References: <283@paisano.UUCP> <156@fesk.UUCP> <3626@islenet.UUCP> <986@edge.UUCP>
Reply-To: richard@islenet.UUCP (Richard Foulk)
Organization: Islenet Inc.,  Honolulu
Lines: 32
Keywords: SysV bugs
Xref: mnetor comp.sys.att:1805 comp.unix.wizards:5510

In article <986@edge.UUCP> hanko@edge.UUCP (Jim Hanko) writes:
> [...]
> The fix involves checking whether the search began at inode 0 when no free
> inodes were found.  If it didn't, then re-start the search at 0. If it
> did, THEN print "out of inodes" and exit. 
> 
> This problem rarely shows up on "normal" file systems, but the high level
> of activity in net file systems seems to aggrivate it. 

Great!  Looks like we may be closing in on a solution here.  Maybe.

So the question is: do you have diffs for the fix?

Since quite a number of people with a few different versions of
System V have reported encountering this problem, it seems that
the ialloc routine you mentioned probably hasn't changed across
versions of unix.  Does that seem like a reasonable assumption?

Since only rnews seems to provoke this bug is there some sort of
way to avoid the bug that comes to mind?

I've just finished running fsck on my news file system for about
the 8th or 10th time today -- all for one days batch of news.

Any insights into a solution or work-around are appreciated.

Thanks.


-- 
Richard Foulk		...{dual,vortex,ihnp4}!islenet!richard
Honolulu, Hawaii