Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!pyrdc!gmu90x!dolqci!vrdxhq!umd5!uvaarpa!virginia!boole!slb
From: slb@boole.acc.virginia.edu (sandy)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Wierd 3b inode problem with news.
Message-ID: <317@boole.acc.virginia.edu>
Date: Wed, 4-Nov-87 22:44:53 EST
Article-I.D.: boole.317
Posted: Wed Nov  4 22:44:53 1987
Date-Received: Tue, 10-Nov-87 01:54:08 EST
References: <283@paisano.UUCP>
Reply-To: slb@boole.acc.virginia.edu
Organization: University of Va., Charlottesville, VA
Lines: 19
Keywords: 3b2 inode file system
Xref: mnetor comp.sys.att:1691 comp.unix.wizards:5372


We have had the same problem (frequently running out of inodes on
a  file system when you know darn well there should be inodes left.
Fsck always complains about bad free inode count.)  with the file
system that hold our news and mail and print queues.  We have a few
3B15's, a few 3B5's and lots of 3B2's.  We don't run news on the
3B2's, and I don't think I have ever observed the problem there, but
all the other machines exhibit this behavior.  I don't see how 
remaking the partition with more inodes can cause this - rather I
think that there is some bug in the file system code and the high
activity that you see in a spool type partition somehow causes a
race condition to happen.  And boy, is it ever a drag - especially
when it happens to a machine that you count on to feed ten other 
machines.  You didn't say what release you run - we run 3.0 on the 
2's, 2.0 on the 5's and 2.1 on the 15's.  
-- 
sandy bryant
slb@virginia.edu
uunet!virginia!slb