Hi I looked at the log of revision comments and found that the broken revision is purely adding files that are from another repository at a particular revision number. I'm in the process of get a copy of that repository.
I took a dump of the repository with the corrupt revision up to that broken revision. When I tried to take an incremental dump from after that revision to head, a few revisions got dumped, but I then received the "Can't read length line in file" error for the broken revision. I'm trying to fix the repository using the solution described in the archives here <http://svn.haxx.se/users/archive-2006-05/0896.shtml>, where I'd reproduce the broken revision. I there a way to get a copy of the all the revisions after the broken one to apply to a new repository? Thank you Trevor On 9 July 2014 11:18, Trevor Dearham <trevor.dear...@gmail.com> wrote: > Hi > > I'm using Subversion 1.6.9 via the CollabNet Subversion Server. When > trying to check out part of the repository I had an error and saw the > following in the Apache logs: > > [Wed Jul 09 10:26:35 2014] [error] [client X] Provider encountered an > error while streaming a REPORT response. [500, #0] > [Wed Jul 09 10:26:36 2014] [error] [client X] A failure occurred while > driving the update report editor [500, #200002] > [Wed Jul 09 10:26:36 2014] [error] [client X] Can't read length line in > file Y [500, #200002] > > The revision that is failing is about 49 MB and was created in 2009. > Subversion is hosted on Windows Server 2003. > > Looking through the mailing list archive, I see 3 options: > > - restore a backup, which hasn't worked > - dump before the damaged revision, after the damaged revision and > then reproduce the change. Unfortunately I don't know all that was changed > in this revision, due to it occurring 5 years ago > - if you are willing to look at it > - provide you the revision > - provide you an output of a script > > I know that this is an old version of Subversion, so would I be able to > recover the file or part of the file, or would the only solution be to > start a new repository with what I can recover? > > Thank you > Trevor >
