Dangling inode problem

[David Hinds]

I'm not sure if this is strictly an Irix problem, but I certainly seem to
have found a file system bug.  After having to power down our machine a
few days ago to restart it, the resulting fsck activity produced a directory
entry in /lost+found that does not point to anything.  A file called '000258'
shows up if I do 'ls', but 'ls -l' complains that the file does not exist.
I have done everything I could think of to get rid of this dangling entry -
'rm', 'unlink', etc. all fail.  I can't create another file of the same name
on top of it.  I am completely at a loss - I suspect that since 'fsck' made
it, it won't be able to undo the damage.  This is a real pain because any
recursive search of the directory tree returns errors - 'find', 'bru', etc
all return failure statuses - which is screwing up all sorts of shell scripts.
How do I get rid of this dang thing?

 -David Hinds
  dhinds at cb-iris.stanford.edu