Return-Path: 
 <users-return-21184-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-users-archive@minotaur.apache.org
Delivered-To: apmail-subversion-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 80E9D10A01
	for <apmail-subversion-users-archive@minotaur.apache.org>;
 Thu,  3 Apr 2014 17:29:06 +0000 (UTC)
Received: (qmail 8678 invoked by uid 500); 3 Apr 2014 17:29:04 -0000
Delivered-To: apmail-subversion-users-archive@subversion.apache.org
Received: (qmail 7861 invoked by uid 500); 3 Apr 2014 17:29:01 -0000
Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@subversion.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@subversion.apache.org>
List-Post: <mailto:users@subversion.apache.org>
List-Id: <users.subversion.apache.org>
Delivered-To: mailing list users@subversion.apache.org
Received: (qmail 7841 invoked by uid 99); 3 Apr 2014 17:28:58 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 17:28:58 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [192.109.42.8] (HELO einhorn.in-berlin.de) (192.109.42.8)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 17:28:53 +0000
X-Envelope-From: stsp@stsp.name
Received: from jim.stsp.name (jim.stsp.name [217.197.84.42])
	by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-4) with ESMTP id s33HSLWS012648
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
	Thu, 3 Apr 2014 19:28:22 +0200
Received: from jim.stsp.name (localhost [127.0.0.1])
	by jim.stsp.name (8.14.8/8.14.7) with ESMTP id s33HSK3H022826;
	Thu, 3 Apr 2014 19:28:20 +0200 (CEST)
Received: (from stsp@localhost)
	by jim.stsp.name (8.14.8/8.14.7/Submit) id s33HSJan023238;
	Thu, 3 Apr 2014 19:28:19 +0200 (CEST)
Date: Thu, 3 Apr 2014 19:28:19 +0200
From: Stefan Sperling <stsp@elego.de>
To: Tobias Bading <tbading@web.de>
Cc: users@subversion.apache.org
Subject: Re: strange E/W200033 (b)locking error/warning when trying to modify
 a svn 1.8 working copy over SMB share
Message-ID: <20140403172819.GA6767@jim.stsp.name>
Mail-Followup-To: Tobias Bading <tbading@web.de>,
	users@subversion.apache.org
References: <533D7904.7000500@web.de>
 <533D7D2E.402@wandisco.com>
 <5A7DF9EA-9CC7-49EC-AA86-2545E803902B@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A7DF9EA-9CC7-49EC-AA86-2545E803902B@web.de>
User-Agent: Mutt/1.5.22 (2013-10-16)
X-Virus-Checked: Checked by ClamAV on apache.org

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.