From owner-freebsd-stable Mon May 6 12:10:01 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA01640 for stable-outgoing; Mon, 6 May 1996 12:10:01 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA01635 for ; Mon, 6 May 1996 12:09:58 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id MAA24695 for ; Mon, 6 May 1996 12:09:57 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA18363; Mon, 6 May 1996 13:05:31 -0600 Date: Mon, 6 May 1996 13:05:31 -0600 From: Nate Williams Message-Id: <199605061905.NAA18363@rocky.sri.MT.net> To: michael butler Cc: nate@sri.MT.net (Nate Williams), stable@freebsd.org Subject: Re: FS corruption during rm -fr In-Reply-To: <199605061829.EAA01152@asstdc.scgt.oz.au> References: <199605061730.LAA18033@rocky.sri.MT.net> <199605061829.EAA01152@asstdc.scgt.oz.au> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > An easy way to recreate this bug is to check out the world, and then > > remove it all. It will *always* leave at least one or two directories > > that an un-removable. 3 passes of fsck in single-user mode are > > necessary to clean this up, .. > > This seems to be two problems .. a quirk in the kernel plus a reference > count problem for which Terry's been trying to get a patch into fsck for > some time. fsck should "fix" it the first time .. Agreed on both counts, but I don't remeber Terry's fsck patch ever being posted. I tried to peruse the mailing lists, but the Net is hosed up and I couldn't get to it. I'll look later if the net comes up. Nate