If you look at the FAQ on the Berkeley DB site, the problem with shared media
is that Berkeley DB uses mmap to map a file into memory, and there is no way to
share this memory between nodes, so it is possible for nodes to conflict no
matter how your storage is shared. The problems are in sharing of memory not the
media itself. This is how I understood the faq anyways.
-Alan
-----Original Message-----
From: Sergey A. Lipnevich [mailto:sergey@optimaltec.com]
Sent: Monday, November 24, 2003 9:09 PM
To: Greg Thomas; users@subversion.tigris.org
Subject: Re: Subversion & NAS
You should probably push for SAN then, EMC does that of course, but I'm not sure
about Celerra. Or use something like iSCSI to make it look like DAS to Berkeley
DB.
HTH.
Sergey.
Greg Thomas wrote:
> We're currently using CVS for about a dozen developers with a
> repository ~1GB big (though a lot of that is Windows DLLs - storing
> these helps resolve DLL hell problems, IME). I'd like to migrate this
> to Subversion, and to that effect I've been offered a properly managed
> system, but, because it is policy, the underlying file system will be
> an EMC Celerra (sp?) NAS system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 25 08:00:59 2003