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

Crash after large deltas

From: John Goerzen <jgoerzen_at_complete.org>
Date: 2003-04-07 22:44:54 CEST


I'm getting some problems, typically when svn_load_dirs runs svn
update after a particularly large changeset goes in:

/home/jgoerzen/svn_load_dirs/upstream/svn_load_dirs.pl: /usr/bin/svn
update failed with this output:
svn: Berkeley DB error
svn: Berkeley DB error while reading node revision for filesystem
Cannot allocate memory
Sometimes, I can then run svn update again, and it will work fine;
however, future commands of all types will randomly fail. I generally
solve the problem with svnadmin dump / reload, though for a repository
of my size, this can take hours. Ths problem is occuring with
increasing frequency and becoming increasingly annoying.

I have tried bumping up the log sizes in DB_CONFIG, but it seems to
have not helped at all. I am using 0.20.1.

-- John

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 7 22:46:03 2003

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

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