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

Re: 0.37 dump/load problems

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-02-10 18:41:22 CET

On Tue, 2004-02-10 at 11:20, Ben Collins-Sussman wrote:

> I don't know why the OS killed the process; maybe the memory footprint
> was too big, trying to commit a 112MB file? It shouldn't be. I'm
> recovering the repository now and re-trying the commit.

$ svn st
M file1
M md5sum.txt

$ svn ci -m "blah"
Sending file1
subversion/libsvn_client/commit.c:677: (apr_err=160028)
svn: Commit failed (details follow):
subversion/libsvn_repos/commit.c:114: (apr_err=160028)
svn: Out of date: 'file1' in transaction '6a'

Apparently the commit succeeded in the repository, and then the svn
client was killed before it finished deltifying or updating the
working copy.

After updating and reverting the conflict, I appended another 1 meg to
the file (making it 113MB in size) and committed by hand. I watched
the svn client in 'top', and the memory footprint stayed fixed at 6MB
the whole time. The CPU usage started out around 50%, then after a
minute or so it spiked up to 95%, then went back down to 8%. After
another minute of waiting, the commit succeeded fine.

So at the moment, I have no idea why commit #112 failed in the first
place. :-(

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 9 00:13:24 2004

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

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