> -----Original Message-----
> From: dev-return-3090761+mr_kernel=163.com_at_tortoisesvn.tigris.org
> [mailto:dev-return-3090761+mr_kernel=163.com_at_tortoisesvn.tigris.org] On
> Behalf Of Stefan Küng
> Sent: Tuesday, November 04, 2014 3:58 AM
> To: dev_at_tortoisesvn.tigris.org
> Cc: Gunter.Koenigsmann_at_semikron.com
> Subject: Re: ra_serf: An error occourred during decompression
>
> On 03.11.2014 17:25, Gunter Koenigsmann wrote:
> > Dear list,
> >
> > I have a big (several Gigabytes large) repository that I cannot check
> > out or update any more without downgrading my system a lot and
> > upgrading again later: svn versions > 1.7.0 return ra_serf: An error
> > occourred during decompression at random places inside it. The result
> > ist that the working copy is locked and a cleanup normally results in
> > a repository tortoisesvn no more recognizes as being one.
> >
> > What I already did was to ask our IT department to deactivate the
> > deflate compression of our apache. I was convinced that this would
> > resolve the problem since ra_serf is a http access library. Seems like
> > I was wrong this time. In the issue tracker of serf I found:
> > https://code.google.com/p/serf/issues/detail?id=152 Don't know if that
> > might be the problem, though.
> >
> > Unfortunately I cannot share the repositorie's contents with the
> > outside world. But I am willing to run several tests to track the
> > problem down. What can I do?
> > I have already tested the last nightly build and it still shows the
> > problem;
> >
> > If I downgrade tsvn on a system, then upgrade it (and the working
> > copy) step by step - upgrading from a new revision to another new
> > revision seems to work well. But if I upgrade to old revisions I have
> > a chance of running into the problem again that increases the older the
> revision is.
> > Might just be that older revisions mean more data and therefore a
> > higher probability to trigger the error and therefore a false-positive.
> >
> > What I also can tell is that I use https to transfer the repository
> > and that I do this without having any proxy between me and the server.
>
> Try a nightly build.
> http://nightlybuilds.tortoisesvn.net/1.8.x/
> it's linked with serf 1.3.8 which has the issue 152 fixed.
>
I have checked issue 152.
But in my case, the whole working copy is 40G, but when I update a single
folder of my working copy, its size is 814M, far from 4G, I also get the
error report. Why do I get this error report either?
> If that doesn't help, then at least we know that it's not that issue
that's at
> fault.
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest interface to (Sub)version control
> /_/ \_\ http://tortoisesvn.net
>
> ------------------------------------------------------
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessage
> Id=3090761
>
> To unsubscribe from this discussion, e-mail:
> [dev-unsubscribe_at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3090849
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-11-05 11:34:41 CET