[
https://issues.apache.org/jira/browse/SVN-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417251#comment-16417251
]
Philip Martin commented on SVN-4730:
------------------------------------
Bad references in the rep-cache could have led to corrupt revisions files in
the past but will not do so in current Subversion. The new behaviour is a
result of the SHA1 collision detection code. When a rep-cache reference is
found Subversion now compares the expanded text obtained from the reference
with the text being committed, if they do not match the commit fails with a
checksum error.
> 'svnadmin verify' should check rep-cache refers to valid revs
> -------------------------------------------------------------
>
> Key: SVN-4730
> URL: https://issues.apache.org/jira/browse/SVN-4730
> Project: Subversion
> Issue Type: Improvement
> Components: svnadmin
> Reporter: Julian Foad
> Priority: Major
>
> In some cases of a damaged repository, it is possible for the rep-cache to
> contain references to revision numbers greater than the head revision.
> For example, this can happen if the most recent revision(s) in a repository
> are unwanted or corrupted, and I attempt recovery by deleting the unwanted
> revisions and rolling back the "current" file.
> 'svnadmin recover' (since 1.7.3, 1.8.0) prunes the rep-cache, but we cannot
> guarantee it was used.
> The consequences of such bad references are serious: they can cause future
> commits to be corrupted, silently.
> Therefore 'svnadmin verify' should check the rep-cache only refers to
> existing revisions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
