[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unable to commit a file of size 4GB to svn repo

From: sathish Sarvepalli <mirchisathu_at_gmail.com>
Date: Tue, 30 Dec 2008 10:33:29 +0530

Kevin, Stefan,

Thanks for your help.

I did try with serf but got the same "Request Entity too large" error. When
I read the log the content length seems to hold a negative value as kevin
mentioned. It is *Content-Length: -371974493*.

Kevin,

/////I did observe this DOES work correctly using the svn:// protocol, if
that is an option.../////

How do i set the svn protocol with TSVN?

Thank you all once again for your help, time and efforts.

Thanks,
Sathish

On Tue, Dec 30, 2008 at 7:57 AM, Kevin Radke <kmradke_at_gmail.com> wrote:

> Stefan Kueng wrote:
> > sathish Sarvepalli wrote:
> >> Stefan,
> >>
> >> Thanks for your immediate response.
> >>
> >> I was told that it is the client that doesnt support the large file
> >> (something to do with neon) not with server since subversion1.5 supports
> >> unlimited file size for commit. Am i missing something here please
> advice.
> >
> > I don't think that neon is the problem. But you can switch to serf
> easily:
> > * Settings dialog->Network. Edit the servers file (click edit button)
> > * add the line 'http-library = serf'
> > * save the file
> >
> > Now TSVN (and all svn clients) will use serf instead of neon.
> > Serf itself uses the apr library, which on Windows is always compiled
> > with large file support.
> >
> > But I still think it's a server problem since 4GB is the maximum size of
> > a file if large-file support is not compiled into the apr lib. And if
> > you're using an FSFS repository, then one revision equals one file - and
> > you're adding a 4GB file in one revision...
>
> This is indeed a svn client library problem. It can easily be seen
> by capturing the http client request with a network protocol analyzer.
> The request clearly shows a negative size being sent by the client in
> the http header. I reported it to the svn list awhile ago, but no
> resolution was found at the time. (I started debugging it, but quickly
> got lost in some unfamiliar svn code.)
>
> We have some 20GB+ sized transactions done over http. The limitation is
> the compressed delta size of one individual file in the transaction.
> (At the time I didn't test serf, but if both exhibit the problem, then
> it is a problem with the common code that computes the file size to be
> placed in the http header.)
>
> FYI, I tested 1.5 versions of TortoiseSVN, command line from windows,
> command line from Linux (both 32 and 64 bit redhat) and command line
> from Solaris, and all exhibited the same problem to servers running on
> Linux, Solaris, and Windows.
>
> I did observe this DOES work correctly using the svn:// protocol, if
> that is an option...
>
> Kevin R.
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=995436
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=995485

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2008-12-30 07:59:05 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.