Please pardon my liberal snippage below:
On May 9, 2007, at 16:48, Matt Sickler wrote:
> > On 5/7/07, Ryan Schmidt wrote:
> >
> >> On May 7, 2007, at 07:59, David Ferguson wrote:
> >>
> >> > Could you guys take a look at my plan for setting up a Subversion
> >> > server farm and let me know if you see any gotchas?
> >> This plan sounds similar to what I've been thinking of, though
> having
> >> the svnserves access the repository via NFS is probably a bad idea.
> >> In my setup, I will be using a SAN, which should not have any of
> the
> >> problems typically associated with NFS.
> the idea is that no matter what server you use (svnserve for svn://
> and apache for http:// and https://), the server access a local
> hard disk for the repo - if it has to use the network to get at it
> and/or you have multiple servers trying to use the same repo,
> problems WILL arise eventually
My understanding of SANs is that they are seen by the OS the same way
that a local hard disk is seen, and also that it is perfectly safe
for multiple machines to attempt to read from and write to files on
the SAN concurrently, because the SAN will manage these requests in a
way that prevents problems. And though the server does have to use a
network to get the data, it's (ideally) a network dedicated to
handling SAN traffic, so it's no worse than accessing the data from,
say, a SCSI disk on a SCSI "network" (bus). Therefore, I understood
that it is perfectly safe (and wonderful) to host a Subversion
repository on a SAN accessed by any number of servers. I believe I
recall reading messages on this list some time ago from someone who
was doing this successfully. However, I should reiterate that I have
not attempted this setup myself yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 08:28:07 2007