the problem was that there was no such file, or du would've picked it up, yet df was reporting the size to be so large. it occurred just after I deleted a buch of large file on /var. I'm guessing that df has a cache that reads from and it didn't update the cache... is that the case? or possibly that the memory blocks themselves continued to be reserved for files that no longer existed, but for some reason when I restarted apache, whose executable and data resides on var, the reservations were removed? It's no longer a serious problem, but I'm just curious what caused it in the first place. any ideas?
-venkman