Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Aug 2013 18:27:41 -0700 (PDT)
From:      Don Lewis <truckman@FreeBSD.org>
To:        linimon@FreeBSD.org
Cc:        freebsd-fs@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject:   Re: kern/181375: [softupdates] disk free space blackhole magic
Message-ID:  <201308190127.r7J1Rf0r017576@gw.catspoiler.org>
In-Reply-To: <201308190115.r7J1Fhx8073716@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201308190127.r7J1Rf0r017576>