Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!ucsfcgl!babar.mmwb.ucsf.edu!srp From: srp@babar.mmwb.ucsf.edu (Scott R. Presnell) Newsgroups: comp.sys.sgi Subject: Re: Dangling inode problem Message-ID: Date: 1 Dec 90 21:28:20 GMT References: <1990Dec1.194910.9878@portia.Stanford.EDU> Sender: daemon@cgl.ucsf.edu Lines: 21 dhinds@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@cgl.ucsf.edu University of California UUCP: ...ucbvax!ucsfcgl!srp San Francisco, CA. 94143-0446 Bitnet: srp@ucsfcgl.bitnet