Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!sri-spam!ames!elroy!cit-vax!genghis!sns
From: sns@genghis.UUCP (Sam Southard)
Newsgroups: comp.unix.xenix
Subject: Re: directory gets stomped
Message-ID: <340@genghis.UUCP>
Date: Tue, 8-Dec-87 12:41:40 EST
Article-I.D.: genghis.340
Posted: Tue Dec  8 12:41:40 1987
Date-Received: Sun, 13-Dec-87 12:44:04 EST
References: <861@ssc.UUCP>
Organization: California Institute of Technology, Pasadena
Lines: 27
Keywords: inodes full xenix null bug

In article <861@ssc.UUCP>, fyl@ssc.UUCP (Phil Hughes) writes:
> The following has happened twice on our system since going to release 2.2.1.
> It appears to happen when you run out of either disk space or inodes.
> My guess is inodes but I am not sure. Has anyone else seen this?
> 
> 	The second byte of a filename in the root directory of a file
> 	system gets stopmed on by a NULL.  For example, the first time
> 	this happened (on our root filesystem) the entry for lib got
> 	wiped out bu the i getting stomped with a NULL.  The next time
> 	this happened (on a mounted file system) the l in dlc got stomped
> 	on by a NULL.  dlc was the fourth entry in this directory, I 
> 	am not sure but I think lib was the fourth in the root filesystem.

This has happened to me, too.  In my case it was /usr/b[i\0]n.  It is inode
number 4 as well.  However, I had plenty of inodes and some disk space left
at the time.  I had had my system up for over a year at the time, so I wasn't
too worried since it was easy to fix - I'm not going to worry about having to
adb /dev/usr once in a year.  However, if it happens a lot it might be
something to worry about.

Does anyone know what's going on?

By the way, my version of Xenix is the one IBM puts out as 2.00.
-- 

Sam Southard, Jr.
{sns@genghis.caltech.edu|sns@genghis.uucp|{backbone}!cit-vax!genghis!sns}