Problem solved. Just wanted to post back so folks having the same
problem might benefit from my wasted day of troubleshooting.
Turned out that a few files in my FSFS repo had gotten corrupted. I had
backups (thankfully), so I just replaced those couple files giving me
problems in 'svnadmin verify' with the backups, and that was that.
There was one other file giving me problems (turned up as: "svn:
E175002: REPORT of '/svn/reponame/!svn/me': Could not read chunk size:
Secure connection truncated (https://mycomp:53239)" ). I looked in the
windows event logs for the VisualSVN Server events, and turned out there
were permission problems. I changed the permissions on the
corresponding file in the repo/db/revs file to match all the other files
in there (it must have gotten corrupted too), and now i'm running great.
Hope someone can benefit from my experience.
allie
On 11/9/2012 3:14 PM, Alexander Shenkin wrote:
> Hello Folks,
>
> I was getting an error while trying to checkout a directory, and some
> investigation with VisualSVN's server manager turned up an error in a
> couple of files ("Corrupt node-revision '5-2893.0.r2893/0' Missing id
> field in node-rev").
>
> I then ran svnadmin verify, and got the following:
>
> ...
> * Verified revision 2433.
> * Verified revision 2434.
> * Verified revision 2435.
> svnadmin: E160004: Revision file (r2436) lacks trailing newline
>
> Looking online seems to indicate that this might have to do with
> commits > 4GB, though that was an old problem. Given that more than 1
> file was problematic in the server manager, I figure there might be
> more than one corrupted revision. The damaged files aren't critical
> and haven't changed since being committed for the first time. I have
> working copies of them.
>
> Any thoughts about how I might go about repairing the repo?
>
> Thanks,
> Allie
>
> VisualSVN Server 2.5.2
> svn 1.7.7
> Win 7 Pro x64 SP1
> TortoiseSVN 1.7.10
Received on 2012-11-10 13:44:40 CET