repozo: a truncated .deltafs results in a corrupted Data.fs on recovery, instead of an error
Bug #906057 reported by
Marius Gedminas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ZODB |
New
|
Undecided
|
Unassigned |
Bug Description
You can truncate a *.deltafs in the middle, and repozo -R doesn't notice
-- it goes on to produce a corrupt Data.fs.
AFAIU the *.dat file contains enough information to do basic sanity
checking for the sizes of the various *.deltafs files. It'd be nice if
repozo -R noticed and aborted with a loud complaint when one of the
files is truncated. Checksum checking would be even nicer, but,
perhaps, expensive, and so maybe ought to require an extra command line
option to enable.
To reproduce:
git clone git://github.
cd repozo-testcases
make test2
To post a comment you must log in.
I'm implementing a `repozo --verify` option to check *.fs/*.deltafs integrity against the *.dat file.