Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sunybcs!boulder!fesk!sverre
From: sverre@fesk.UUCP (Sverre Froyen)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Wierd 3b inode problem with news.
Message-ID: <156@fesk.UUCP>
Date: Fri, 6-Nov-87 10:48:39 EST
Article-I.D.: fesk.156
Posted: Fri Nov  6 10:48:39 1987
Date-Received: Sun, 8-Nov-87 16:05:37 EST
References: <283@paisano.UUCP>
Organization: SERI, Golden, CO
Lines: 28
Xref: mnetor comp.sys.att:1683 comp.unix.wizards:5365

in article <283@paisano.UUCP>, demasi@paisano.UUCP (Michael C. De Masi) says:
> 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 ....

(text deleted)

>                       ...  When the feed returned to full
> volume, I noticed that I was getting "out of inode" errors
> when I knew full well there weren't nearly that many files
> in the system.  So I unmounted the news file system, fsck'd
> it, got a "free inode count in superblock (fix?)" message
> back from fsck, told it to fix it, remounted the file system
> and again everything went smoothly until the news volume
> dropped again, and the same thing happened.

I have seen the same thing on an ICM3216 running SysV.2.2.
The inode count of the spool file system (where news reside)
will drop from 12000 to 0 within minutes (perhaps seconds) while
unpacking a compressed news batch (rnews -U). Recourse is to go
to single user mode and do an fsck on the file system. This will
restore all (12000) lost inodes.  This scenario happens about
once per month and I have not noticed a correlation with the
news volume.
-- 
Sverre Froyen
UUCP:   boulder!fesk!sverre, sunpeaks!seri!fesk!sverre
ARPA:   froyen@nmfecc.arpa
BITNET: froyen@csugold.bitnet