Xref: utzoo comp.bugs.sys5:574 comp.unix.questions:9395 comp.unix.xenix:3422 Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!seismo!sundc!pitstop!sun!oliveb!elandes!dave From: dave@elandes.UUCP (Dave Mathis @ ELAN designs) Newsgroups: comp.bugs.sys5,comp.unix.questions,comp.unix.xenix Subject: inode amnesia, no disk space and uucico Message-ID: <585@elandes.UUCP> Date: 23 Sep 88 12:13:10 GMT Article-I.D.: elandes.585 Organization: ELAN designs, Saratoga CA Lines: 19 Recently my system lost some inodes and decided that the disk was full (it wasn't). In itself, that wasn't too disasterous, a simple set of fsck's can take care of the results. The real problem started when uucico started up for a news feeding. There were still inodes available so files could be created, but no writes on new files could succeed. HOWEVER, it seems that uucico never checks to see if a write to a TM* file succeeds, it just kept receiving news, not being able to write it and responding to the other system that the file was OK. This has happened on a few occasions, and by loosing the free list, having the file system really fill up, or by a bad write/sector confusing the file system. In general, I think this is antisocial behavior and would expect that uucico would either hang up the conversation or tell the other system that the receive didn't go so well. So, can anyone explain to me what is really happening, and if there is a way to prevent this. The system is SCO Xenix 2.2 (286) on a real IBM AT. Dave Mathis UUCP oliveb!elandes!dave