On Sun, Feb 20, 2011 at 06:11:19PM +0000, Dominic Raferd wrote:
first step, unless the most recent
backup is critical to you, is to try regressing the repository to get it
back to a clean state, with the --check-destination-dir switch
Fatal Error: Destination dir scyw00225 does not need checking
If this refuses to regress, claiming that there is no corruption, I
have a bash script which can 'force' a regression. You can repeat
this as many times as necessary to get past (hopefully) the original
corruption.
So it'll be a "force regression, try --verify, until --verify runs
through", losing one full, probably uncorrupted increment per iteration?