Nicolas Goutte wrote:
>On Monday 13 June 2005 12:25, Olivier Sannier wrote:
>
>
>>Nicolas Goutte wrote:
>>
>>
>>>On Friday 10 June 2005 23:35, Brian C. Van Essen wrote:
>>>
>>>
>>>>Hello, I was trying to get my advisor to use our subversion
>>>>repository today and during what seemed a normal sequence of
>>>>operations, the repository has corrupted itself and we are being
>>>>forced to pull a backup. I am trying to figure out what went wrong,
>>>>so here is the sequence of events.
>>>>
>>>>Background:
>>>>Two of us use the repository mainly via ssh remote access, and have
>>>>had no problems.
>>>>
>>>>Today's sequence of events:
>>>>Today, I had our advisor checkout the repository via a "file://" URL
>>>>
>>>>
>>>>from a nfs mounted drive.
>>>
>>>Have you read the FAQ and the handbook? As far as I have understood, it is
>>>written there that you cannot use Berkeley DB on NFS, not even on a NFS
>>>system claiming to support Berkeley. (And from the logs below, you *are*
>>>using Berkeley, not FSFS!)
>>>
>>>
>>Well, you could, but you would have to NOT use the file:// URL, as this
>>is the source of the problem.
>>
>>
>
>Well, sorry, buf that is not what the Subversion FAQ says.
>
>It tells that Berkeley DB does not work over NFS and the pointed document
>http://www.sleepycat.com/docs/ref/env/remote.html
>tells the same.
>
>So I doubt that it depends on the access method used by the Subversion client.
>If the server uses Berkeley but the database is accessed by NFS, you should
>probably get the same problem.
>
>
Well, I think it is more a problem of multiple access to the same file,
by different processes. So if you have a single acces point (Apache, or
svnserve) and no one uses file:// then it should be fine. That's how I
understand it, but I may be wrong.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 13 15:05:25 2005