Thanks for the info --
So I suppose a single read-write host / and mutiple read-only hosts should
be ok ?
On 9/22/08 7:59 AM, "david.x.grierson_at_jpmorgan.com"
> No - this will not work with NFS access from multiple hosts.
> NFS (even with correctly working locking) does not work with Subversion
> 1.5 or lower because the underlying apr libraries used for transactions
> still use DBM files - which require working locks.
> You will eventually end up with repository corruption - particularly
> likely when large commits are performed.
> David Grierson
> JPMorgan - IB Architecture - Source Code Management Consultant
> GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson_at_jpmorgan.com
> Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
> Murli Varadachari <mvaradachari_at_facebook.com>
> 22/09/2008 15:27
> "users_at_subversion.tigris.org" <users_at_subversion.tigris.org>
> Internal Use <mvaradachari_at_facebook.com>
> Shared storage for subversion repository
> I am testing out an arrangement whereby the subversion repository is
> located on shared partition [ netapps partition ] -- and accessed by
> multiple subversion hosts via NFS. My plan is to have one of these hosts
> be used for read-write access and the rest for read-only access. I have
> tested this out and it looks O.K so far.
> Q: Can this arrangement be used to have all hosts be capable of read-write
> access. Can subversion handle multiple access points on the same
> P.S: I am using FSFS
> Generally, this communication is for informational purposes only
> and it is not intended as an offer or solicitation for the purchase
> or sale of any financial instrument or as an official confirmation
> of any transaction. In the event you are receiving the offering
> materials attached below related to your interest in hedge funds or
> private equity, this communication may be intended as an offer or
> solicitation for the purchase or sale of such fund(s). All market
> prices, data and other information are not warranted as to
> completeness or accuracy and are subject to change without notice.
> Any comments or statements made herein do not necessarily reflect
> those of JPMorgan Chase & Co., its subsidiaries and affiliates.
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure
> under applicable law. If you are not the intended recipient, you
> are hereby notified that any disclosure, copying, distribution, or
> use of the information contained herein (including any reliance
> thereon) is STRICTLY PROHIBITED. Although this transmission and any
> attachments are believed to be free of any virus or other defect
> that might affect any computer system into which it is received and
> opened, it is the responsibility of the recipient to ensure that it
> is virus free and no responsibility is accepted by JPMorgan Chase &
> Co., its subsidiaries and affiliates, as applicable, for any loss
> or damage arising in any way from its use. If you received this
> transmission in error, please immediately contact the sender and
> destroy the material in its entirety, whether in electronic or hard
> copy format. Thank you.
> Please refer to http://www.jpmorgan.com/pages/disclosures for
> disclosures relating to UK legal entities.
Received on 2008-09-22 18:58:21 CEST