Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!zaphod.mps.ohio-state.edu!uwm.edu!spool.mu.edu!olivea!isc-br!frigg!carlp From: carlp@frigg.isc-br.com (Carl Paukstis) Newsgroups: comp.unix.bsd Subject: corrupted directory, can't remove Summary: Need a way to fix my filesystem Keywords: help Message-ID: <carlp.723695363@frigg> Date: 7 Dec 92 02:29:23 GMT Sender: news@isc-br.isc-br.com (news user) Organization: ISC-Bunker Ramo, An Olivetti Company Lines: 23 Nntp-Posting-Host: frigg.isc-br.com This is the second time it's happened. Some directory got corrupted for bad reasons (me fooling around with my hardware config; this time I added RAM over 16Mb, which I thought might be foolish...). Now, fsck reports that this directory is corrupt, "salvages" it, and goes happily on. Unfortunately, the directory is STILL corrupt, as reported by subsequent invocations of fsck. Trying "rmdir" and "rm -rf" both report the directory is not empty, but "ls -al" only shows . and .. So, I can't pass fsck, and I can't get rid of the directory. I CAN rename it (it's now /tmp/bad). I can't open it or unlink it from a C program (the program just hangs on the open() or unlink()). My experience is all with SYSV; someone suggested "clri()", but I don't see any such under 386BSD. The last time this happened, I was about to clear and rebuild my disk anyway, but I'd prefer not to do that again. Any suggestions? -- Carl Paukstis, RRR&RSG | "The good news is that Clinton will have to ISC-Bunker Ramo / Spokane, WA | work very hard to do worse than Bush in terms Phone: +1 509 927-5439 | of economic policy. The bad news is that he Mail: carlp@mail.isc-br.com | will probably manage to do so." - Ed Ipser