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

Re: svn Windows network filesystem limitations, any workarounds?

From: Daniel Patterson <danpat_at_danpat.net>
Date: 2005-04-10 12:59:01 CEST

scott wrote:
> Subversion runs perfectly well on Windows. The only major limitation I can
> see is that it won't work with network filesystems. For me now, this isn't a
> big problem, but at some point I will need to find a solution.

   That is true if you use the BDB backend. But as of Subversion 1.1,
   a different backend, FSFS works just fine on network filesystems.

   I have set it up on a network share with 4 Apache servers in
   round-robin DNS. We had no problems. Just do:

     svnadmin create --fs-type fsfs repository

> 2. At some point you would reach the limit of how many massive drives you
> could load into a single server.
> You could have svn1.blah.com and svn2.blah.com and host them on different
> servers but you still have the problem of a single point of failure and then
> you also have to worry about managing and backing up a growing number of
> separate critical servers, argh.

   You could always setup a reverse proxy which hands requests for
   different servers back to different repository machines. mod_proxy
   and the ProxyPass and ProxyPassReverse, or mod_rewrite with the [P]
   flag would do the trick. All clients just talk to the reverse proxy
   machine, never directly to the backend hosts.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 10 13:03:09 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.