Hmm, I don't think that was the case for me. I wasn't removing files in any strange way, and later, after doing some more work, df was reporting closer to 200%. After rebooting, df reports this:
main: df main: 33,783,808 used + 477,184,000 free = 510,967,808 (6.6% used) Which seems to make sense, but now I'm even more confused about the output I was getting before: main: df main: 557,539,328 used + 35,184,325,517,312 free = 510,967,808 (109.1% used) I thought the large number was my disk space including venti. Looking more closely, I certainly don't have 35 terabytes hiding anywhere. On Thu, May 30, 2013 at 4:06 PM, David du Colombier <0in...@gmail.com> wrote: >> Sorry, I think I understand what this number represents now. I thought >> it was a percentage of used disk space in my fossil partition and >> completely separate from venti. > > No, you were right. The Fossil df command returns > the number of used blocks in the Fossil write buffer. > > Df can report used > total if you removed files > without using rm(1) or fossilcons(4) remove. > For example, when you marked blocks available > for allocation with bfree. > > See fl->nused in /sys/src/cmd/fossil/cache.c. > > -- > David du Colombier >
