On Tue, 2009-01-20 at 21:02 -0500, erik quanstrom wrote: > > In such a setup a corrupted block from a fossil > > partition will go undetected and could end up > > being stored in venti. At that point it will become > > venti "problem". > > it's important to keep in mind that fossil is just a write buffer. > it is not intended for the perminant storage of data.
Sure. But it must store the data *intact* long enough for me to be able to do a snap. It has to be able to at least warn me about data corruption. > while corrupt data could end up in venti, the exposure lies only > between snapshots. you can rollback to the previous good > score and continue. That is my *entire* point. If fossil doesn't tell you that the data in its buffer was/is corrupted -- you have no reason to rollback. Thanks, Roman.
