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

Re: database destroyed

From: Blair Zajac <blair_at_orcaware.com>
Date: 2002-11-27 03:54:31 CET

Ben Collins-Sussman wrote:
>
> Petr Sebor <petr@scssoft.com> writes:
>
> > When (just by accident) someone operates with the database - co/up, while
> > dumping the database, it somehow gets always corrupt (so I have to run
> > db_recover on it) or worse, the db/__db.001 ... 005 simply just disappear.
> > The only cure I know is to svnadmin load the dump back in to regain
> > working repository :-(
>
> That makes no sense... the db files *disappear*? Dumping the database
> is just another process that is reading data via libsvn_fs. We should
> have no problem with concurrent db readers. In fact, we expect
> multiple httpd child processes to do this all the time.

Are you using hot-backup.py? It deletes the log files that are no
longer required after they are backed up.

Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 27 03:55:49 2002

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.