Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cornell!rochester!pt.cs.cmu.edu!sei!ajpo!ebeser
From: ebeser@ajpo.sei.cmu.edu (Eric Beser)
Newsgroups: comp.unix.microport
Subject: Re: . and .. get blown away when directory size > 65536 UPORT286
Summary: uucp can blow away the directory
	 . and .. not found
Keywords: Microport System V/AT bug, may be generic to 286 Unix
Message-ID: <347@ajpo.sei.cmu.edu>
Date: 28 Jun 88 13:28:48 GMT
References: <2104@sugar.UUCP>
Lines: 27

In article <2104@sugar.UUCP>, karl@sugar.UUCP (Karl Lehenbauer) writes:
> I'm not exactly sure that this is what happened, but it appears that when
> a directory reaches 65536 bytes in size under Microport System V/AT it
> wraps around and the next two files created cause . and .. to get blown
> away, trashing the directory.
> 
I have had this problem when usenet sends large amounts of files. I have
found  a multitude of problems caused by this. I noticed that other
directories in the inode chain get blown away too.

> I used fsdb to change the size of the directory to zero then let fsck trash
> all the files.  I think it would be possible to trash a couple entries
> in the directory then create valid . and .. files.  I don't know if the
> kernel assumes they're the first two files.  It might be a good idea to
> assume it does.

Would someone please tell me how to use fsdb to do this. I am sitting
with a system with about 10 directories that have been trashed.
The manual has no indication of how to use fsdb. Is there any books that
have more detailed information that I can read? 

Thanks.

Eric Beser
Westinghouse ESG
arpa : ebeser@ajpo.sei.cmu.edu
usenet:eric@sarin.UUCP
(301)-765-1360