Hi Anatoly,
can you build a custom version of the serf library used by your svn
client to enable logging?
Attached patch should enable the logging needed, I hope it should
clarify the original " internal malfunction" error you reported
earlier.
You can send the log output to me privately, probably will be a big file.
On Thu, Jul 11, 2013 at 12:04 PM, Anatoly Zapadinsky
<zapadinsky_at_gmail.com> wrote:
> I've increased swap size to 8gb, increased opened files handles limit to
> 200k and ran the process at night when the server is not very busy.
>
> Finally svnsync form a revision copy in db, but hang after it. It didn't
> print "Committed revision" just hanged on a set of dots after "Transmitting
> file data....". I've killed it and ran "svnadmin verify". The revision copy
> seems to be fine. And it was successfully packed by svnadmin pack at the end
> of mirroring process.
>
> svnsync is a buggy crap! I guarantee this. And no one cares. No one going to
> opened an issue.
I propose *you* open an issue in the issue tracker
(http://subversion.tigris.org/issue-tracker.html). We'll need some
more information though, especially the platform of both your client
and server, and the exact svnsync init and svnsync sync commands you
use (without username & password info, that's not needed).
regards,
Lieven
>
>
> On Tue, Jul 9, 2013 at 3:30 PM, Anatoly Zapadinsky <zapadinsky_at_gmail.com>
> wrote:
>>
>> svnsync failed to sync repository with a single commit containing 56000
>> files. This commit handled perfectly by console svn and tortoise svn. We can
>> checkout this folder structure and so on. But when I tried to sync this
>> commit to the local mirror repository it fails.
>> 32 bit version of svnsync crashed with out of memory exception.
>> 64 bit version made a transaction folder containing 117000 files in it,
>> allocated like 3gb of memory and finally crashed with this diagnostic: "svn:
>> E235000: In file 'subversion/libsvn_ra_serf/util.c' line 1649: internal
>> malfunction".
>> May be this commit is not an example of the best practice but it crash
>> only svnsync all the other svn tools handle it perfectly.
>> What should I do? How to mirror this repository? Is it a bug or not?
>
>
Received on 2013-07-11 12:25:19 CEST