Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!rsiatl!jgd From: jgd@Dixie.Com (John G. DeArmond) Newsgroups: comp.unix.sysv386 Subject: Re: The INfamous inode bug Message-ID: <5685@rsiatl.Dixie.Com> Date: 7 Jan 91 20:30:05 GMT References: <43@esacs.UUCP> <45@esacs.UUCP> Organization: Rapid Deployment Systems (making go-fast things and things that-go fast) Lines: 26 pizzi@esacs.UUCP (Riccardo Pizzi) writes: >Hmmm... I'm running ISC 2.2 from 3 month now (I've ran 2.0.2 for about >one year without problems) and I'm spooling a *lot* of news every night >(about 1,5-2 Mb). >I didn't notice anything strange with my filesystem. >Are you sure it was not a problem with your hw? THAT's not a lot of news, THIS is a lot of news (Whips out his traffic report) :-) We averaged 10 mb/day throughout the month of December up to the Christmas break. We usually run from 4 to 6 mb/day. The Inode bug gets us about twice a week. I have a cron job that runs every 10 minutes that looks at the inode count and when it hits the emergency level (10,000 on our system) it fusers everybody off the news partition and runs fsck. I get a printout of the activity on our logging printer so I can see when it happens. When the volume was up around 10 mb/day, it got us almost every day. There is a binary patch available for 2.2, though I've not yet applied it. John -- John De Armond, WD4OQC | "Purveyors of speed to the Trade" (tm) Rapid Deployment System, Inc. | Home of the Nidgets (tm) Marietta, Ga | "To be engaged in opposing wrong offers but {emory,uunet}!rsiatl!jgd | a slender guarantee of being right."