Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!bloom-beacon!gatech!galbp!wittsend.lbp.harris.com!mhw
From: mhw@wittsend.lbp.harris.com (Michael H. Warfield (Mike))
Newsgroups: news.admin
Subject: Re: The Inode-Eating Bug
Message-ID: <8883@galbp.LBP.HARRIS.COM>
Date: 10 Oct 89 03:47:00 GMT
References: <906@zorch.SF-Bay.ORG> <231@rsiatl.UUCP> <1989Oct7.213314.17921@twwells.com> <282@rsiatl.UUCP> <1989Oct9.140605.21949@twwells.com>
Sender: news@galbp.LBP.HARRIS.COM
Reply-To: mhw@wittsend.UUCP (Michael H. Warfield (Mike))
Organization: Lanier Network Knitting Circle - Thaumaturgy & Speculums Division
Lines: 33

In article <1989Oct9.140605.21949@twwells.com> bill@twwells.com (T. William Wells) writes:

>I had the following experience:

>	run out of inodes
>	fsck the file system
		.
		.

>So the answer is: it has happened.

	Ok so I've got a REAL STUPID question, but I've been there TOO!

	DID YOU UNMOUNT THE FILE SYSTEM FIRST ??????

	If you don't, chances are you are right, fsck will do little or nothing
useful.  Until I made sure all news activity was finished; the file system
was not busy; and I had unmounted the file system, frequent fsck's did not
cure the problem.  Doing all of the above finished the job.

	I haven't seen the scripts in question and I developed my own
procedures through painful experience (the inode problem is only one of
several that I have had to work around).

	If this is your root file system that your running fsck on in multi
user mode, may the saints look kindly upon you and pray for your safety.
It shouldn't do any harm until it finds something it needs to fix right in the
middle of something you need to use or have in use.

Michael H. Warfield  (The Mad Wizard)	| gatech.edu!galbp!wittsend!mhw
  (404)  270-2123 / 270-2098		| mhw@wittsend.LBP.HARRIS.COM
An optimist believes we live in the best of all possible worlds.
A pessimist is sure of it!