Could not read chunk size. Error in SVN

Question

I have recovered SVN repository from crashed PC and now I can checkout files from few directories but in one place during checkout it says:

Error: REPORT of '/svn/RepTest/!svn/vcc/default': Could not read chunk size: 
Secure connection truncated (https://mypc:8443) 

Could anyone help me, how to fix that repository? Thanks!

Answer 1

I've just had the same error when trying to update a checkout to the latest revision. Some fiddling about revealed that it was one particular file causing the issue. For example:

root
  - A
    - AFileInFolderA.h
    - AnotherFileInFolderA.h
  - B
    - AFileInFolderB.h
  - C
    - AFileInFolderC.h

With the repo structure above, AFileInFolderA.h was the problem file. I came to this conclusion because I could do and svn update in folders B and C but not on the root or folder A. Drilling down further, I could update AnotherFileInFolderA.h but not the problem one.

Anyway, with that information in hand I copied my working copy changes from folder A, then (using Tortoise SVN) did a selective Update To Revision on the root folder, excluding folder A from my checkout. I then did the reverse, re-adding the folder to the checkout. Finally I added my local changes back in and committed to the repo. All is now working fine.

Answer 2

When checking out I got the same error. The problem was indeed with specific revisions, so I did a workaround. It seemed that the revisions that raised the error had a long path. Another look on the specific revisions got me to think it might not need to be under source control. These files were generated automatically upon every build. I just kept another copy of the entire directory in a 'Deprecated' folder, and deleted the problematic files/folders. After the deletion, checkout was OK.

Answer 3

I had the same error recently:

REPORT of '/svn/.../!svn/vcc/default': Could not read chunk size: Secure connection truncated.

We are using Tortoise SVN and I was the only one in the team that had the issue. Since the problem didn't prevent me from committing my changes, I did just that. Next I removed the folder with the project from my hard drive. Then I created it again and made an "SVN checkout".

This is what fixed it for me.