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

Re: [PATCH] Re: BerkeleyDb on NetApp NFS [#14837]

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2006-06-28 22:00:53 CEST

Keith Bostic wrote:
> I'd suggest the following wording:
> If you are using a repository with the Berkeley DB back end (default
> for repositories created with Subversion 1.0 and 1.1, not the default
> thereafter), do not access the repository via NFS. Althought Berkeley
> DB supports database storage on remote file systems, not all Subversion
> functionality with be available in this configuration.

Hrm. "Not all Subversion functionality will be available" seems a bit
vague, and still leads folks to believe that there's some Subversion-related
value to be had in putting their BDB-backed repositories on NFS (of which I
can fathom none). I think the key points to make here are:

   * you CANNOT safely access an NFS-hosted Subversion repository from
     multiple NFS clients, period.

   * you CAN safely access an NFS-hosted Subversion repository from a single
     NFS client if, and only if, the NFS implementation is up to par. (What
     was the criteria, here -- ability to support file-backed shared memory
     regions, or something?)

   * you CAN configure your repository to house its database and logfiles
     on NFS, but some Subversion functionality won't work (due to
     shortcomings in Subversion). And of course, since the repository
     itself isn't on NFS, it isn't accessible via any NFS clients.


C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 28 22:01:38 2006

This is an archived mail posted to the Subversion Dev mailing list.