Berkeley DB logfile cleanup

[cm...@collab.net]

Today I was loading a dumpfile of the svn.collab.net Subversion
repository into a new repos on my home computer.  Periodically, I was,
in another shell window, running db_archive -a and removing the
unnecessary logfiles.  But at one point in my 'svnadmin load', there
was a period of several hundred revisions that flew by where
db_archive -a reported nothing -- that is, it was not safe to remove
any logfiles -- yet my logfile count grew to about 160 of them on
disk.  

Any ideas what's keeping us from finalizing the log files for such a
long period of time?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Berkeley DB logfile cleanup

[Michael Price <mi...@acm.org>]

cmpilato@collab.net wrote:
> Today I was loading a dumpfile of the svn.collab.net Subversion
> repository into a new repos on my home computer.  Periodically, I was,
> in another shell window, running db_archive -a and removing the
> unnecessary logfiles.  But at one point in my 'svnadmin load', there
> was a period of several hundred revisions that flew by where
> db_archive -a reported nothing -- that is, it was not safe to remove
> any logfiles -- yet my logfile count grew to about 160 of them on
> disk.  
> 
> Any ideas what's keeping us from finalizing the log files for such a
> long period of time?

I don't know but I've seen something similar before. I usually just stick a 
checkpoint in there (i.e. "db_checkpoint -1 ; db_archive | xargs rm")

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org