Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!att!news.cs.indiana.edu!msi.umn.edu!cs.umn.edu!kksys!wd0gol!newave!john From: john@newave.UUCP (John A. Weeks III) Newsgroups: comp.unix.sysv386 Subject: Re: The INfamous inode bug Message-ID: <575@newave.UUCP> Date: 5 Jan 91 05:49:11 GMT References: <43@esacs.UUCP> Reply-To: john@newave.mn.org (John A. Weeks III) Organization: NeWave Communications Ltd, Eden Prairie, MN Lines: 24 In article <43@esacs.UUCP> pizzi@esacs.UUCP (Riccardo Pizzi) writes: >In article pete@fidata.fi writes: > > Is the famous inode-lost bug finally fixed in ISC 2.2.1 release? Or is it > > still "a known bug"? > Can someone please tell me about this bug? I am running 2.2.0 and would like > to know if there is something I should be aware of. I never experienced > bugs with file system till now. Some versions of UNIX, even AT&T code, had a bug that caused the number of inodes to suddenly become zero even though there were many unused. Running fsck would restore the correct free inode count. Heavy USENET activity often makes the problem show up in the partition that holds the news spool directory. By the time one figures out that there is a problem, it is too late--bytes fall on the floor because UNIX thinks the file system is full. This problem exists in ISC version 2.0.2. -john- -- =============================================================================== John A. Weeks III (612) 942-6969 john@newave.mn.org NeWave Communications ...uunet!rosevax!tcnet!wd0gol!newave!john ===============================================================================