From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 00:04:19 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2053316A4CE; Tue, 1 Mar 2005 00:04:19 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF5F43D2F; Tue, 1 Mar 2005 00:04:18 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id j2100MVp099889; Mon, 28 Feb 2005 19:00:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)j2100LTj099885; Mon, 28 Feb 2005 19:00:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Mon, 28 Feb 2005 19:00:21 -0500 (EST) From: Jeff Roberson To: Alfred Perlstein In-Reply-To: <20050228235123.GC81082@elvis.mu.org> Message-ID: <20050228185955.V50530@mail.chesapeake.net> References: <20050228235123.GC81082@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: mckusick@mckusick.com cc: jeffr@freebsd.org cc: Xin LI cc: fs@freebsd.org Subject: Re: ffs softdeps fix request X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 00:04:19 -0000 On Mon, 28 Feb 2005, Alfred Perlstein wrote: > There's an artifact of ffs softupdates that causes issues if a crash > occurs while deleting or creating files. > You should really ask Kirk about this sort of thing. > Basically, one can wind up with a directory that is empty, but the > link count is artificially high. Then you can have a directory > that is empty, but not removeable. It would be somewhat trivial > to add some code to check the directory's contents when a VOP_RMDIR > would have failed because of the link count check. > > But then my head went all explody when trying to figure out how > that would impact the background fsck in progress. > > Any ideas? > > -- > - Alfred Perlstein > - Research Engineering Development Inc. > - email: bright@mu.org cell: 408-480-4684 >