repozo -B twice in quick succession may produce a broken backup; repozo -R will not notice
Bug #906058 reported by
Marius Gedminas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ZODB |
New
|
Undecided
|
Unassigned | ||
Bug Description
Two frequent runs of repozo -B may create a .fs and a .deltafs with the same timestamp, which condition then causes repozo -R to silently produce a corrupt (truncated) Data.fs.
If there's a timestamp collision between two .deltafs files, repozo -B aborts with an error, which is fine by me.
To reproduce:
git clone git://github.
cd repozo-testcases
make test1
To post a comment you must log in.
