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

Re: Weird db_dump/db_load behaviour on a svn db

From: Michael Wood <mwood_at_its.uct.ac.za>
Date: 2003-06-30 14:01:04 CEST

On Sun, Jun 29, 2003 at 11:44:59AM +0100, Max Bowsher wrote:
> A previous post here mentioned using db_dump and db_load to compact the
> component databases of a subversion fs. Curious, I decided to test this,
> with the following rather strange results:
> 1) Dump the strings db to a file. OK.
> 2) Try to load the dump into a new db file ("stringsnew"). Fails with a
> large amount of scary error messages, and leaves behind a stringsnew file
> which is far too small.
> 3) Rerun the load. It gives one warning, and then completes successfully.
> 4) Verify success by re-dumping and comparing with the first dumpfile.
> Which really is just bizzarre.
> Has anyone experienced anything like this?
> Cygwin, WinXP, db-, svn r6360.
> 1) $ db_dump strings > sdmp
> 2) $ db_load stringsnew < sdmp
> db_load: Lock table is out of available locks
> db_load: Not enough core

This probably means you don't have enough locks and/or RAM for this
operation to complete successfully? Maybe try tweaking stuff in the

Just a guess.

Michael Wood <mwood@its.uct.ac.za>
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 30 14:02:11 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.