*BSD News Article 8649


Return to BSD News archive

Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!wupost!uunet!pipex!warwick!doc.ic.ac.uk!uknet!cf-cm!myrddin.isl.cf.ac.uk!paul
From: paul@isl.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Re: corrupted directory, can't remove
Keywords: help
Message-ID: <1992Dec8.172156.13138@cm.cf.ac.uk>
Date: 8 Dec 92 17:21:54 GMT
References: <carlp.723695363@frigg>
Sender: news@cm.cf.ac.uk (Network News System)
Organization: Intelligent Systems Lab, ELSYM, Universiity of Wales, College of 
              Cardiff.
Lines: 29

In article <carlp.723695363@frigg> carlp@frigg.isc-br.com (Carl Paukstis) writes:
>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?

These are exactly the symptoms that I got when applying ALL the patches
after installing 0.1, I eventually had to re-install the system.

As a matter of interest what patches do you have. When I re-installed I
avoided the disk patches and it's never happened again.

clri is in /sbin/clri, I tried this and it did remove the problem inode
but when I was subsequently able to do a fsck there was so much damage
that I just re-installed everything!