Confused file name in directory

[ron at brl-sem.UUCP]

In article <105 at aob.UUCP>, jim at 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