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

Re: Having to recover after every commit

From: Mike Olensky <mike_at_aretoo.com>
Date: 2005-02-28 22:45:59 CET

Jaime Ruiz wrote:

>I really hope someone has any ideas what i can do to fix my repository.
>I've recreated the repository several times by dumping the old
>repository and loading the dump into a new repository. It seems that
>everytime I commit (I am using TortoiseSVN as the client), the commit
>works. However, if I then try to browse the repository I get a the
>typical Berkeley DB error run recovery. The recovery works but it is
>not ideal to have to recover after every commit. I don't think it is
>a permissions issue since i am the only person who has been accessing
>the repository. This is a recent development and has been working
>great for the previous 40 revisions.
>I am running subversion 1.1.3 on Fedora 3.
>Anyone have any ideas?
>jaime ruiz

I had a similar problem in my SuSE 9.1 setup and adding the umask 0002
to apache2ctl and doing "chmod g+s db" after repository creation (and
recovery) fixed my problem. For me it was a logfile getting created by
wwwrun:www which would only happen depending on the size of the commits.

Mike Olensky

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 28 22:48:23 2005

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.