Xref: utzoo comp.unix.sysv386:4000 news.software.b:6623 Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!swrinde!elroy.jpl.nasa.gov!ames!sun-barr!newstop!texsun!digi.lonestar.org!dinosaur!root From: root@dinosaur.lonestar.org (Root of all evil) Newsgroups: comp.unix.sysv386,news.software.b Subject: Help! I am experiencing the inode problem... Message-ID: <123@dinosaur.lonestar.org> Date: 14 Jan 91 01:07:07 GMT Followup-To: comp.unix.sysv386 Organization: Dinosaur Dallas, Tx Lines: 32 Vital Information: OS - System V.3.2 / Interactive 3.2 News - Bnews version 2.11.19 Hardware: 25Mhz 386 no-floating point co-processor Disks: Drive 0: 110meg ESDI Contains swap space, /, /tmp, /usr Drive 1: 320meg ESDI Contains /usr2 (/usr2/spool/news /usr2/lib/news) I have been running this version of bnews for over 3 weeks without any problems until today. Today I decided to recover some of my disk space and ran an 'expire -E 15 -e 7'. Seems simple enough but now when I receive news (ie. rnews -U) after distributing news for about 10 minutes I start getting errors about no more inodes available on /usr2 partition. And sure enough when I do a 'df' it says I don't have any, but moments earlier I had over 2000 of them. And as you might expect when I unmount the disk and run fsck it reports a problem with the free inode count and fixes the problem, only until the next run of 'rnews -U'. I remember a while back someone posting about a known problem with Interactive's, and I think SCO's, UNIX inode count and that there was a patch or some fix for it. If this is true I am in desperate need of it. To be honest I don't know if the expire had anything to do with it, but everything was working just find until I did that. Thanks in advance Keith Cantrell ----------------------------------------------------------------------- Keith Cantrell Phones: hm: 214-492-1088; wk: 214-669-2509 keith@dinosaur.lonestar.org or ...!uunet!digi!dinosaur!keith -----------------------------------------------------------------------