Dangling inode problem

[Scott R. Presnell]

dhinds at portia.Stanford.EDU (David Hinds) writes:

>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

[...]

>How do I get rid of this dang thing?

I had the exact same thing happen to me.  While not an optimal fix, another
reboot (and implicit fsck) cleared away the reference.

	- Scott
--
Scott Presnell				        +1 (415) 476-9890
Pharm. Chem., S-926				Internet: srp at cgl.ucsf.edu
University of California			UUCP: ...ucbvax!ucsfcgl!srp
San Francisco, CA. 94143-0446			Bitnet: srp at ucsfcgl.bitnet