[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: strange E/W200033 (b)locking error/warning when trying to modify a svn 1.8 working copy over SMB share

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 3 Apr 2014 19:28:19 +0200

On Thu, Apr 03, 2014 at 07:12:26PM +0200, Tobias Bading wrote:
> I'm quite sure Emacs doesn't fork more than one svn child process in
> parallel,

It doesn't matter how many clients emacs is forking.

As soon as emacs runs an svn client that tries to access the working copy
at the same as any other svn client (run by emacs or something else), one
of the clients will run into an error if exclusive locking mode is enabled.

> single file. Besides, I get the same errors when trying "svn resolved
> <file>" or "svn update" in a shell. I'll do a few tests tomorrow with
> a SMB share on a Windoze machine to see whether I get similar errors
> or not.

Not sure if this is really relevant but using a windows network share
with sqlite is discouraged by the sqlite faq: http://sqlite.org/faq.html#q5

"""
  People who have a lot of experience with Windows tell me that file
  locking of network files is very buggy and is not dependable. If what
  they say is true, sharing an SQLite database between two or more Windows
  machines might cause unexpected problems.
"""

It's possible that this extends to Samba but the wording doesn't make
this entirely clear.
Received on 2014-04-03 19:29:08 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.