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

Re: Frequent database corruption

From: Bastian Blank <bastian+dev=subversion.tigris.org_at_waldi.eu.org>
Date: 2005-02-19 21:12:09 CET

On Sat, Feb 19, 2005 at 08:06:23PM +0100, Michel Jouvin wrote:
> >Which cluster filesystem?
> Tru64/TruCluster Cluster File System. I am not sure about Florian question
> : the file system (including locks) has the whole semantic of a local file
> system but that I am not sure about system mutexes. In fact it is possible
> to create shared memory between cluster nodes but it has to be done
> explicitly.
> Anyway, as I explained below, we now run a configuration where we only have
> one Apache server handling subversion request and I have httpd logs to
> prove that. I understand that there is may be something wrong in our
> configuration if we run several concurrent Apachae instances on several
> nodes accessing the same repositories. But the database corruption we have
> now are not in this configuration and even not related to commit or other
> repository modification.

You have to uses fsfs. Berkeley DB shared memory needs shared mapping
where updates show up in any other mapping. This behavior is not
required by POSIX and is not possible to do with cluster fs without
large overhead.


I'm a soldier, not a diplomat.  I can only tell the truth.
		-- Kirk, "Errand of Mercy", stardate 3198.9
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 19 21:13:15 2005

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.