Date: Fri, 30 Jul 1999 17:09:58 +0930 From: Greg Lehey <grog@lemis.com> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: current@FreeBSD.ORG Subject: Re: An oddity after a panic Message-ID: <19990730170958.C56925@freebie.lemis.com> In-Reply-To: <19990730084127.A1396@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Fri, Jul 30, 1999 at 08:41:27AM %2B0200 References: <19990730084127.A1396@daemon.ninth-circle.org> <xzplnby3870.fsf@flood.ping.uio.no> <19990730084127.A1396@daemon.ninth-circle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 30 July 1999 at 9:31:15 +0200, Dag-Erling Smorgrav wrote: > Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes: >> [note I already did chflags] >> I'd love to hear some ideas about how to solve this. > > # chflags -R 0 /usr/obj/work > # rm -rf /usr/obj/work That doesn't seem to be the answer. And the directory where the problem occurred doesn't normally get any schg flags set. On Friday, 30 July 1999 at 8:41:27 +0200, Jeroen Ruigrok/Asmodai wrote: > Hi, > > I was cleansing /usr/obj after a panic to see if I could reproduce it and > I have this slight oddity: > > [root@daemon:/usr/obj] (32) # rm -rf work/ > rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty > rm: work/FreeBSD/src/gnu: Directory not empty > rm: work/FreeBSD/src: Directory not empty > rm: work/FreeBSD: Directory not empty > rm: work/: Directory not empty > > [root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/ > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll > total 2 > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ../ > > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (35) # cd .. > [root@daemon:/usr/obj/work/FreeBSD/src/gnu] (36) # ll > total 3 > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:33 ../ > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 usr.bin/ That link count for usr.bin looks funny. It should be 2, and that's probably why you can't remove it. > I have no idea what's wrong here. > After the panic however I did get some softupdates inconsistencies, such > as: DUPs, Block counts, even an internal error: dups with -p. Yes, it looks like you have a broken file system. The easy part is to cut off the directory tree a bit further up (say, mv usr.bin to lost+found/andbroken). Actually getting rid of it and reclaiming any lost space will probably be more difficult and involve you in deeper knowledge of fsdb than you really wanted. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990730170958.C56925>