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

Re: svn eats all memory, OOM killer kicks in

From: <cmpilato_at_collab.net>
Date: 2002-04-14 09:11:57 CEST

"Marcelo E. Magallon" <marcelo.magallon@bigfoot.com> writes:

> * I check in
>
> cd ../..
> svn ci -m "Window Maker 0.64.0"
> Adding ...
> Adding ...
> Adding ...
> Transfering .................................................
> .............................................................
> [...]
> ...................Killed

I would not be surprised if you just plain ran outta memory. On the
very top of my current TODO list is the task of examining the
performance of our commit system, which I just rewrote a couple of
weeks ago with (admittedly) no real attention paid to performance.

> * A second check-in attempt produces this:
>
> Adding branches/upstream/util/wmsetup.c
>
> svn_error: #21068 : <File already exists in revision>
> Commit failed (details follow):
>
> svn_error: #21068 : <File already exists in revision>
> file already exists: filesystem `/home/marcelo/tmp/wmaker/svn/db', transaction `3', path `branches/upstream/util/wmsetup.c'

Hm...if the commit failed, then this shouldn't have happend.

> At this point I assume the repository has been corrupted. How can I
> verify or deny this?

You could use the `svnadmin' and `svnlook' tools to see what your
youngest revision is, what paths exist in it, etc. That would be
really useful information.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 14 09:14:44 2002

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