Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!rice!sun-spots-request
From: eplunix!das@harvard.harvard.edu (David Steffens)
Newsgroups: comp.sys.sun
Subject: Re: Dump says corrupted directory in Pass II
Keywords: Miscellaneous
Message-ID: <10247@brazos.Rice.edu>
Date: 25 Jul 90 19:38:08 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n268, Replies: v9n268
X-Sun-Spots-Digest: Volume 9, Issue 281, message 3
Originator: spots@titan.rice.edu

In article <10092@brazos.Rice.edu>,
ballen@csd4.csd.uwm.edu (Bruce Allen) writes:
> The problem seemed to be the file called "!".  When this was 
> removed, dump was happy again.

It can't be quite that simple.  My users are constantly creating files
with wacko names :-) and I have never had any trouble dumping them.  Just
now I made a directory with a file named "!" in it and I was able to dump
the filesystem with no problem.

>>  DUMP: (This should not happen)bread from /dev/rsd3h 
>>			[block 136768]: count=8192, got=-1
>>  DUMP: corrupted directory, inumber 45100

Are you _sure_ the filesystem was good?  You did run fsck, right?  I'm
betting that removing "!" sort of "fixed" whatever was wrong with the
directory or one of the underlying inodes.

If I were you, I'd run fsck again.  And I'd try reading all the blocks of
/dev/rsd3h using "dd" to see if one of them has gone bad.  Finally, I'd
verify that block 136768 is a legal block number for /dev/rsd3.

{harvard,mit-eddie,think}!eplunix!das	David Allan Steffens
243 Charles St., Boston, MA 02114	Eaton-Peabody Laboratory
(617) 573-3748 (1400-1900h EST)		Mass. Eye & Ear Infirmary
	I'm a firm believer in learning from one's past mistakes...
	...but why should it take so many to get a good education?