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

Re: Excessive Repository Size

From: Robert Pluim <rpluim_at_bigfoot.com>
Date: 2003-03-28 14:00:40 CET

Alexander Klyubin writes:
> Hello!
>
> I installed Subversion in order to see how it compares to CVS. To make
> the comparison I added a couple of projects contained in one CVS
> repository to a newly created Subversion repository. (I added the
> projects manually, since cvs2svn script did not work on my CVS
> repository for some reason.)
>
>
> Now comes the strange issue. The size of CVS repository is roughly 100
> MB. The size of Subversion repository containing the very same projects
> is 206 MB.
>
> I took a look 'db' subdirectory of the Subversion repository. Looks like
> the size of 'strings' file corresponds to the size of CVS repository.
> However, there are myriads of log.* files, 1 MB each (one for each
> transaction I made while adding the projects?). Are these log files
> necessary? Is it safe to delete them from time to time (e.g., before
> backup)?

From http://www.sleepycat.com/docs/utility/db_archive.html :

  db_archive [-alsVv] [-h home] [-P password]

  Description

  The db_archive utility writes the pathnames of log files that are no
  longer in use (for example, no longer involved in active
  transactions), to the standard output, one pathname per line. These
  log files should be written to backup media to provide for recovery in
  the case of catastrophic failure (which also requires a snapshot of
  the database files), but they may then be deleted from the system to
  reclaim disk space.

-- 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 28 14:00:55 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.