Path: utzoo!attcan!uunet!ginosko!uakari.primate.wisc.edu!uflorida!novavax!twwells!bill
From: bill@twwells.com (T. William Wells)
Newsgroups: news.admin
Subject: Re: The Inode-Eating Bug
Message-ID: <1989Oct7.213314.17921@twwells.com>
Date: 7 Oct 89 21:33:14 GMT
References: <906@zorch.SF-Bay.ORG> <231@rsiatl.UUCP>
Organization: None, Ft. Lauderdale, FL
Lines: 19

In article <231@rsiatl.UUCP> jgd@rsiatl.UUCP (John G. De Armond) writes:
: This problem is trivially easy to fix regarding news, the most common
: perpetrator of the problem.  Following are a couple of scripts that
: completely solve the problem.

Apologies, but your scripts do little or nothing to solve the problem.

First: the inode crash can occur regardless of the number of available
inodes on your system.

Second: the crash can occur almost instantly after you have done a
fsck, so doing it frequently does not eliminate the problem.

Unless you have the bug fixed, you are always at risk of the inode
crash.

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com