From owner-freebsd-fs@FreeBSD.ORG  Mon Aug 19 01:55:36 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@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 62A17A7A;
 Mon, 19 Aug 2013 01:55:36 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4466C2976;
 Mon, 19 Aug 2013 01:55:35 +0000 (UTC)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id r7J1Rf0r017576;
 Sun, 18 Aug 2013 18:27:44 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201308190127.r7J1Rf0r017576@gw.catspoiler.org>
Date: Sun, 18 Aug 2013 18:27:41 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: kern/181375: [softupdates] disk free space blackhole magic
To: linimon@FreeBSD.org
In-Reply-To: <201308190115.r7J1Fhx8073716@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: freebsd-fs@FreeBSD.org, freebsd-bugs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 01:55:36 -0000

Sounds a lot like the bug that was fixed in head by this commit:

<http://svnweb.freebsd.org/base?view=revision&sortby=date&revision=253998>

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.