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

Re: Severe repository database corruption

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-05 16:13:07 CEST

On Fri, 2004-07-02 at 08:04, Frank Freund wrote:
> Thanks *all* for the help, it seems that the permissions did the trick.
> I will give a final feedback next week.
> But what I don't understand, and that's why I didn't digged in this
> direction yesterday is that the repository worked from its begin on, for
> about 6 months and 400 commits with around 700MB, with *exactly the same
> settings without any problem*.
> So how to explain this? What triggered the error?

The database will get "wedged" if any process accessing it suddenly
dies, as the FAQ explains. So perhaps some apache process crashed while
it had the database open. It could be something as simple as that:
nothing to do with your configuration or setup. The important thing to
learn, as an svn administrator, is that when database gets stuck, you
know how to un-stick it and keep permissions correct (because wrong
permissions will wedge a repository just as easily as a process crash.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 5 16:16:18 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.