Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sunybcs!kitty!larry
From: larry@kitty.UUCP (Larry Lippman)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Wierd 3b inode problem with news.
Message-ID: <2207@kitty.UUCP>
Date: Fri, 6-Nov-87 23:42:01 EST
Article-I.D.: kitty.2207
Posted: Fri Nov  6 23:42:01 1987
Date-Received: Mon, 9-Nov-87 03:53:48 EST
References: <283@paisano.UUCP>
Organization: Recognition Research Corp., Clarence, NY
Lines: 19
Keywords: 3b2 inode file system
Summary: Same problem here...
Xref: mnetor comp.sys.att:1686 comp.unix.wizards:5371

In article <283@paisano.UUCP>, demasi@paisano.UUCP (Michael C. De Masi) writes:
> What I'm starting to wonder is whether or not I have accidentally
> created some sort of stick point in the free inode list that
> can only be gotten around with an fsck?  Because of recent
> fluctuations with my news feed, it has become a real hassle
> to constantly have to fix the file system, so I was wondering
> if anyone out there had ever had a problem like this or a
> possible solution?  Is it something I did or some strange
> interaction between news & Sys V?  Any ideas?

	If it's any consolation, I have the same problem on `kitty', which
is also a 3B2.  The problem indentical to yours occurs about once every
4 to 5 months.  I just reboot and fsck.  It is so infrequent, that I just
haven't felt like tracking it down.

<>  Larry Lippman @ Recognition Research Corp., Clarence, New York
<>  UUCP:  {allegra|ames|boulder|decvax|rutgers|watmath}!sunybcs!kitty!larry
<>  VOICE: 716/688-1231       {hplabs|ihnp4|mtune|seismo|utzoo}!/
<>  FAX:   716/741-9635 {G1,G2,G3 modes}   "Have you hugged your cat today?"