I see this quite a lot on Linux; space taken up on disk (df) but not visible (du) is usually held by a deleted file that is still opened by some process. You can see these with lsof, and a reboot does indeed clear this. If you don't want to reboot, track down the process and kill it, this also releases the handle.
/mr On Wed, Dec 31, 2014, 15:12 Aero 9000 <[email protected]> wrote: Quite odd, the 109M gap between the results of du -sh . (in /var) and du -h, disappeared after a reboot. I can't recall ever having had something like this in Linux, so in DragonFlyBSD I hadn't expected this behaviour at all. Like a dejavu of Windows -- to make it work, reboot.
