anyone else ever seen things like this from fossil? it seems a bit wayward...
# on the fossil console, after `disk full' returned in errors:
main: df
main: 10,046,783,488 used + 35,180,756,598,784 free = 6,431,293,440
(156% used)
main: snapclean 3600
main: df
main: 3,000,909,824 used + 3,430,383,616 free = 6,431,293,440 (46% used)
the server goes into `disk full' state. i think one underlying problem
is that i haven't applied the change to remove floating-point calculations
from fossil's timer routine, and thus at least sometimes it can never quite
get to the right time to do the snapclean itself. even so, i've only seen
this effect since i updated fossil in january after several years.
i've had periodic `disk full' problems since then.
