You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by scott <sc...@projxpert.com> on 2005/04/10 08:49:29 UTC

svn Windows network filesystem limitations, any workarounds?

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.

There are two impacts of this that I can see:

1.You can't have redundancy or load balancing
  If the computer with the svn repository crashes, fails or cant handle the
demand the best you
could offer is read-only access to your last backup until the server is
recovered.


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.

Does anyone know if there is a workaround to this, or potentially this could
be resolved in the future. Maybe at that point its time to migrate to a
non-Windows architecture. Im not against moving it but I need to look at all
the
options first.

Thanks in advance for your help.

s.

Projxpert.com  - Software Project Hosting


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn Windows network filesystem limitations, any workarounds?

Posted by Daniel Patterson <da...@danpat.net>.
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.

daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn Windows network filesystem limitations, any workarounds?

Posted by John Szakmeister <jo...@szakmeister.net>.
On Sunday 10 April 2005 04:49, 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.

With the introduction of the FSFS backend in 1.1.0, the problem of network 
drive access went away for the most part.  The only requirement is that 
the network drive support locking.

http://subversion.tigris.org/faq.html#nfs

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org