lae@ernest.UUCP (Alan Edmonds) (03/17/89)
I have an intermitent free inode problem unbatching a compressed news
feed. During a rnews -U run from cron, I start getting the following
errors in the log file.
Mar 16 13:08 killer received <451@corpane.UUCP> ng rec.autos subj 'Driver Testing (was Re: Worst highway events)' from sparks@corpane.UUCP (John Sparks)
Mar 16 13:08 killer Cannot open /usr/spool/news/.tmp/.ara29834 (w): No space left on device
Mar 16 13:08 killer received <506@skep2.ATT.COM> ng sci.space.shuttle subj 'Re: List of Shuttle missions' from slr@skep2.ATT.COM (Shelley.L.Rosenbaum.[ho95c])
Mar 16 13:08 killer Cannot open /usr/spool/news/.tmp/.ara29835 (w): No space left on device
Mar 16 13:08 killer received <452@corpane.UUCP> ng rec.games.frp subj 'Re: 25 Types of Players.' from sparks@corpane.UUCP (John Sparks)
Mar 16 13:08 killer Cannot open /usr/spool/news/.tmp/.ara29836 (w): No space left on device
The errlog file:
Mar 16 13:08 <451@corpane.UUCP> inews: Cannot open /usr/spool/news/.tmp/.ara29834 (w): No space left on device
Mar 16 13:08 <506@skep2.ATT.COM> inews: Cannot open /usr/spool/news/.tmp/.ara29835 (w): No space left on device
Mar 16 13:08 <452@corpane.UUCP> inews: Cannot open /usr/spool/news/.tmp/.ara29836 (w): No space left on device
Mar 16 13:08 <507@skep2.ATT.COM> inews: Cannot open /usr/spool/news/.tmp/.ara29837 (w): No space left on device
Mar 16 13:08 <42423@clyde.ATT.COM> inews: Cannot open /usr/spool/news/.tmp/.ara29838 (w): No space left on device
Mar 16 13:08 <42424@clyde.ATT.COM> inews: Cannot open /usr/spool/news/.tmp/.ara29840 (w): No space left on device
I have a seperate partition for /usr/spool/news and it looks like this:
/usr/spool/news (/dev/dsk/c1d3s0 ): 34338 blocks 19117 i-nodes
total: 114146 blocks 32000 i-nodes
I seem to have plenty of room (and inodes).
DUring the run, I start getting the "out of space" errors and
a df shows 0 inodes avalable. I kill rnews, umount /usr/spool/news
and run fsck on it. fsck say "FREE INODE COUNT WRONG IN SUPER-BLK FIX ?"
or something like that. I say yes and remount it.
The mounted filesystem says 19117 inodes free.
I figure it's either a bad block on the disk in the super-blk area,
a bug in news (or my version), or another program corrupting the
super-blk.
Any ideas ? Is this a problem with news ?
I am running System V release 3.0 and news 2.11 patchlevel 17.
This is a real irritating problem. I would appreciate any
insight offered.
Thanks in advance.
---
Alan Edmonds Texas Instruments, Inc.
My opinions are only my own. M/S 3105
UUCP: [killer|rpp386]!ernest!lae 8505 Forest Lane
Work phone: (214)480-2365 Dallas, Texas 75243bill@twwells.uucp (T. William Wells) (03/17/89)
In article <890@ernest.UUCP> lae@ernest.UUCP (Alan Edmonds) writes:
: I have an intermitent free inode problem unbatching a compressed news
: feed. During a rnews -U run from cron, I start getting the following
: errors in the log file.
You have run into the Dreaded System V Inode Bug!
This is a kernel bug. AT&T has screwed us all by having not fixed
this known bug, which has existed for years.
If you are running Microport V/386 3.0e, I have a kernel patch that
will fix this. Other people may have patches for other systems. As
a last resort, if you are good with a disassembler finding the right
place to patch isn't too hard.
Good luck.
---
Bill
{ uunet | novavax } !twwells!bill
(BTW, I'm going to be looking for a new job sometime in the next
few months. If you know of a good one, do send me e-mail.)