Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!IRO.UMontreal.CA!matrox!zap!fortin
From: fortin@zap.uucp (Denis Fortin)
Newsgroups: comp.unix.sysv386
Subject: Re: The INfamous inode bug
Message-ID: <1991Jan8.044007.1837@zap.uucp>
Date: 8 Jan 91 04:40:07 GMT
References: <43@esacs.UUCP> <5685@rsiatl.Dixie.Com> <652@chiton.ucsd.edu>
Organization: zap, Montreal
Lines: 19

In article <652@chiton.ucsd.edu> dorman@chiton.ucsd.edu (Leroy M. Dorman) writes:
>In article <5685@rsiatl.Dixie.Com>, jgd@Dixie.Com (John G. DeArmond) writes:
>> pizzi@esacs.UUCP (Riccardo Pizzi) writes:
>> >Hmmm... I'm running ISC 2.2 from 3 month now [...] I didn't notice anything
>> >strange with my filesystem. Are you sure it was not a problem with your hw?
>> 
>> [inode bug bites us a couple of times a week]
>> John De Armond, WD4OQC        | "Purveyors of speed to the Trade"  (tm)
>
>There are other things which can look like the "inode bug". [...]

Nah...  It's *the bug*!  I used to be bitten by the "infamous inode
bug" on System V/AT about once a week, so after I upgraded to ISC
2.0.2 and I realized that that old "friend" was still in there, I
applied the binary patch and have been living happily ever since...

-- 
Denis Fortin, DMR Group Inc, (514) 877-3301 (All of these opinions are my own)
fortin@zap.uucp   uunet!sobeco!zap!fortin   fortin%zap@larry.mcrcim.mcgill.edu