I've observed 3 instances of similar errors when using the 1.8.5 svnadmin verify on 3 different old repositories. (the hundreds of other repos on this server verified in 1.8.5 without problems.)
svnadmin: E160004: r97's root node's predecessor is r90 but should be r96 svnadmin: E160004: r502's root node's predecessor is r483 but should be r501 svnadmin: E160004: r22033's root node's predecessor is r22031 but should be r22032 All 3 of these repositories verify without errors using 1.7.5. All 3 of the revisions are from different months in 2009, when I assume the server was running 1.6.something. The repositories were "upgraded", but not a full dump/load between major version upgrades. svn 1.8.5 can serve the existing repositories without any observed errors. I can use a 1.8.5 svnsync to a new repository which then verifies without errors. Is this just a case of svnadmin verify in 1.8.5 being too conservative and should be issuing a warning instead? All 3 repositories are quite large (over 200GB each) and have the same fsfs format: cat format 5 cat db/format 4 layout linear Obviously I could "fix" the error by doing a full dump/load cycle, but I'm interested in figuring out more about the cause. I can't provide the repo due to size and content, but I'm happy to dig around some of the files for more information. Also, on a slightly related note, why does the new svnadmin verify medatadata portion not always start at r0 or even show consecutive revision numbers on repositories with large numbers of revisions? Thanks! Kevin
