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

Re: [converting scarab] high repository size after cvs2svn

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-02-01 13:31:24 CET

On Sunday 01 February 2004 07:08, Jerome Lacoste wrote:
> Hi,
> The scarab project [1] has decided to give SVN a go.
> I played with cvs2svn yesterday. My current problem is the repository
> size which is about 8 times higher than the corresponding CVS one.
> I am using subversion 0.33 which is the current version in Debian
> unstable.
> [snip]
> A newer version, probably 0.37, should come really soon in the
> repository according to the maintainer [2]. I will upgrade ASAIC.
> To convert, I did the following:
> [snip]
> jerome@dolcevita> du -sk cvs svn
> 235784 cvs
> 1991752 svn
> In other words, subversion uses much more space than cvs in the
> repository (> 8 times).
> I couldn't find any reference to such issue in the issue system.
> I am completely new to subversion so I perhaps made a mistake and missed
> an option/config.
> Perhaps 0.37 will help, as 0.33 still uses BDB 4.1 in Debian. 0.37 will
> use 4.2; should that help?
> Would be happy if someone could shred some light on this issue?

There are several things that you should be aware of. First, did you clean
the log files after converting the repository? While cvs2svn does it's
thing, it commits to the repository leaving behind log files. You need to
use 'svnadmin list-unused-dblogs' to get a list of the unused log files that
you can safely delete. BDB 4.2.x takes care of this problem by automatically
removing log files itself. I imagine that you didn't do this, and that's why
your repository looks so large.

Second, stay away from BDB 4.1.x. We've seen database problems from people
that have been using that version. Apparently there are some issues with
their shared memory implementation that causing sporadic repository
corruption. I highly recommend using BDB 4.2.50. You'll get some speed
improvements, and automatic log removal which makes it a little easier to

Finally, our latest version is always the best. You'll probably find little
change in cvs2svn, but there have been a number of user-visible changes since
0.33.0 in the command line tool. Be careful if you takes this step though,
you will need to 'dump' the repository and 'load' it after you upgrade. An
example of how to do this is in the FAQ at:


I hope that answers some of your questions!


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 1 13:32:59 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.