Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!brl-adm!brl-sem!ron
From: ron@brl-sem.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix
Subject: Re: Confused file name in directory
Message-ID: <650@brl-sem.ARPA>
Date: Wed, 25-Feb-87 22:35:12 EST
Article-I.D.: brl-sem.650
Posted: Wed Feb 25 22:35:12 1987
Date-Received: Sat, 28-Feb-87 01:45:03 EST
References: <105@aob.UUCP>
Organization: Electronic Brain Research Lab
Lines: 12
Xref: utgpu comp.unix.questions:1187 comp.unix.wizards:1132 comp.unix.xenix:117

In article <105@aob.UUCP>, jim@aob.UUCP (Jim Anderson) writes:
> name?  Fsck doesn't find anything wrong with the file, and I can't unlink
> the file because unlink can't find 'D\0c'.

ls -i will give the inode number.  Run clri on that inode and follow
it up with FSCK.  If you really want it back you can probably use dump
and restore to fish it out.

You could probably poke the block on the raw device, but this is likely
to be more trouble than it is worth.

-Ron