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

Re: Repository corruption with two access on repository

From: Saulius Grazulis <grazulis_at_ibt.lt>
Date: 2005-04-07 09:04:56 CEST

On Wednesday 06 April 2005 18:36, Manuel VACELET wrote:

> > I tried with subversion 1.1.4, error messages seems more relevant:
> I now try with fsfs backend and it works.

Could it be that accessing repository over file:// resets ownership of the
database or directories, and after apache is not permitted to access the

With fsfs you don't notice this since every revision (delta) is stored in a
separate file, and you do not need to write thas file any more, right?

Similar, when we run subversion over svn+ssh://, the Subversion Book says our
repository has to have permissions for group to write into it -- if we want
every user to commit under his/her own name. And the server runs under umask
002 so that new files remain group writable.

> Well, but not very convenient.

Why? FSFS is nice -- you just look into db/revs/, and immediately see what
revisions you have there, and rsync shows you what has been backed-up.
Honestly, I do not see any charm in big f(l)at databases... ;).

Dr. Saulius Grazulis
Institute of Biotechnology
Graiciuno 8
LT-02241 Vilnius
Lietuva (Lithuania)
fax:          (+370-5)-2602116
tel.: office: (+370-5)-2602556
      mobile: (+370-684)-49802, (+370-614)-36366

  • application/pgp-signature attachment: stored
Received on Thu Apr 7 12:10:13 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.