James Prestwood wrote:
> I'm attempting to fix a corrupt repository which is reporting "Checksum
> mismatch while reading representation"
Thanks for bring this issue to the dev list, James.
I was the author of "fsfsfixer". I'd be grateful however if any other
devs could comment or assist.
I am involved in trying to both debug and fix this corruption.
> (the possible cause has been
> raised by Julian - https://svn.haxx.se/dev/archive-2017-01/0080.shtml).
(That's very unlikely to be the cause, actually.)
> I'm wanting to run the fsfsfixer script
> from https://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/fsfsfixer/
> but this isn't compatible with repositories created in 1.8+, as per the
> error I'm seeing:
> ('error:', FixError("Filesystem '/path/to/repo/db' is too new (format
> 6); try the version at
We haven't determined yet whether the checksum mismatch is because the
data is corrupted or just the checksum is wrong. The desire to use
fsfsfixer (which, if it works on FSFS f6, can rewrite the stored
checksum) is based on an assumption of the latter, and/or that we don't
really care that much if the content is corrupted because the files are
mostly build results that don't often need to be referred to again.
> I see there is the setting "MAX_FSFS_FORMAT = 5" in the file
> fixer/fix-rev.py whiuch I could in theory change to 6, but I don't know
> if the format is too different to get away with this.
I have a feeling we discussed this before but can't currently find the
discussion. Anyone remember?
> For good measure, here is some information about the repo:
> UUID: bf4578a2-f9f2-0310-8dae-8c7b66b38d95
> Repository Format: 5
> Compatible With Version: 1.8.0
> Repository Capability: mergeinfo
> Filesystem Type: fsfs
> Filesystem Format: 6
> FSFS Sharded: no
> FSFS Logical Addressing: no
Received on 2017-01-30 15:47:47 CET