Kirk McKusick 824009a16a 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. This bug manifested itself in the Postgres server which would leak/lose hundreds of files per day amounting to many gigabytes of disk space. This bug required shutting down Postgres, forcibly unmounting its filesystem, remounting its filesystem and restarting Postgres every few days to recover the lost space. Reported by: Dan Thomas and Palle Girgensohn Bug-fix by: kib Tested by: Dan Thomas and Palle Girgensohn MFC after: 2 weeks		2013-08-06 16:50:05 +00:00
..
ffs	With the addition of journalled soft updates, the "newblk" structures	2013-08-05 22:02:45 +00:00
ufs	This bug fix is in a code path in rename taken when there is a	2013-08-06 16:50:05 +00:00