SVN Repo breaks on huge commits?

[Constantin Werner <we...@cs.uni-goettingen.de>]

Dear all,

I think there might be a bug in SVN. I've done a huge commit.
The size of this commit was larger then 120 Megabytes. It looks like
this triggered a bug in Subversion that leads to a broken "rev" file.
Unfortunately, this is not a standard Berkeley DB file, and "svnadmin
recover" cannot repair it.
The effect of this broken rev file is that users (when accessing via 
https+svn) get the following error message on updates:

"could not read chunk size: secure connection truncated"

This seems to be a bug in SVN that gets triggered with large
files [2] - but the post below is rather old already. Is there anything 
known about this?

Thank you

Best regards,
Constantin

[1] http://svn.haxx.se/users/archive-2005-09/0149.shtml
[2] http://svn.haxx.se/users/archive-2005-10/0001.shtml

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org