Re: AW: Corrupted FSFS commit

Kutter, Martin wrote on Fri, 26 Feb 2010 at 10:29 +0100:
> The reported numbers are unstable, and flip between positive and
> negative values.

They don't have any reason to differ across runs, do they? So, what's
next? Uninitialized memory? Valgrind? (and how to make it play nicely
with pools, I don't rememeber)

> First, I think that the error should have been reported
> on commit, not on checkout.

You can run verify/dump automatically on every commit to help catch
these errors.

> I'm afraid the commit just got corrupted somehow - is there a way to
> remove/replace it in the repository?

If 1.6.5 dumps without aborting, I suppose you could dump/load with
svndumpfilter to remove the added path. Or you could configure authz
rules to prevent you from seeing the 'problematic' added path, and then
run svnsync as usual (it would ignore paths that aren't authz-readable
for it).

Daniel
Received on 2010-02-26 12:57:24 CET