Re: [9fans] Fossil; is the time right?

[rog@vitanuova.com]

it's been stable for me...  for all of two days, running it on my
laptop :-).  it's survived lots of rebooting, and kernel crashing,
with no probs, as advertised.

it seems quite a lot slower than kfs (a naive measurement showed that
it read 15MB 50% slower than kfs).  presumably this will change if
it gets a read cache.

i have one query about its integrity: soft updates preserve the
integrity of the write buffer; venti is log structured, and has no
problem with being killed.

however, i wonder if it's possible to "lose" a block in between fossil
and venti if one is running venti -w.  e.g.  fossil writes a block to
venti, marks it as archived, reuses that block, and then the machine
crashes before venti has got around to actually writing the block.

how does fossil guard against such an eventuality?

  cheers,
    rog.