Date: Mon, 19 Aug 2013 03:00:01 GMT From: Mark Linimon <linimon@lonesome.com> To: freebsd-fs@FreeBSD.org Subject: Re: kern/181375: [softupdates] disk free space blackhole magic Message-ID: <201308190300.r7J301j1093160@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/181375; it has been noted by GNATS. From: Mark Linimon <linimon@lonesome.com> 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 <truckman@FreeBSD.org> ----- Date: Sun, 18 Aug 2013 18:27:41 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> 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: <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. ----- End forwarded message -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201308190300.r7J301j1093160>