From owner-freebsd-fs@FreeBSD.ORG Mon Aug 19 03:00:02 2013 Return-Path: Delivered-To: freebsd-fs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 16EBB111 for ; Mon, 19 Aug 2013 03:00:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 059C42C1C for ; Mon, 19 Aug 2013 03:00:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7J301fm093162 for ; Mon, 19 Aug 2013 03:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7J301j1093160; Mon, 19 Aug 2013 03:00:01 GMT (envelope-from gnats) Date: Mon, 19 Aug 2013 03:00:01 GMT Message-Id: <201308190300.r7J301j1093160@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org Cc: From: Mark Linimon Subject: Re: kern/181375: [softupdates] disk free space blackhole magic X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Linimon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2013 03:00:02 -0000 The following reply was made to PR kern/181375; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/181375: [softupdates] disk free space blackhole magic Date: Sun, 18 Aug 2013 21:55:48 -0500 ----- Forwarded message from Don Lewis ----- Date: Sun, 18 Aug 2013 18:27:41 -0700 (PDT) From: Don Lewis To: linimon@FreeBSD.org cc: freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org Subject: Re: kern/181375: [softupdates] disk free space blackhole magic Sounds a lot like the bug that was fixed in head by this commit: Log Message: This bug fix is in a code path in rename taken when there is a collision between a rename and an open system call for the same target file. Here, rename releases its vnode references, waits for the open to finish, and then restarts by reacquiring its needed vnode locks. In this case, rename was unlocking but failing to release its reference to one of its held vnodes. The effect was that even after all the actual references to the vnode had gone, the vnode still showed active references. For files that had been removed, their space was not reclaimed until the filesystem was forcibly unmounted. ----- End forwarded message -----