Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of andy.levy@gmail.com
 designates 209.85.213.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20140613132829.GA11059@petamem.com>
References: <20140613132829.GA11059@petamem.com>
From: Andy Levy <andy.levy@gmail.com>
Date: Fri, 13 Jun 2014 09:41:27 -0400
Message-ID: 
 <CALb=wn=z2m4rZ=yMTEcj=9=hDKx18aJQhou2uUzKQ808b14PHw@mail.gmail.com>
Subject: Re: svn mv and svn cp fails in 1.8.8 and 1.8.9
To: Richard Jelinek <rj@petamem.com>
Cc: "users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: text/plain; charset=UTF-8

On Fri, Jun 13, 2014 at 9:28 AM, Richard Jelinek <rj@petamem.com> wrote:
> Hi,
>
> when I try to cp or mv a directory within a repository, I get (after
> several seconds of waiting with no cpu/disk activity) the following
> error.
>
>
>
> rj@sol$ svn cp .test_equ_simple/ /opt/PetaMem/PMLS/active/data/lexica/c/e/s/
> svn: E200033: Another process is blocking the working copy database,
> or the underlying filesystem does not support file locking; if the
> working copy is on a network filesystem, make sure file locking has
> been enabled on the file server
> svn: E200033: sqlite[S5]: database is locked
> svn: E200033: Additional errors:
> svn: E200033: sqlite[S5]: database is locked
>
>
> the sandbox is then in a "L" state and has to be "svn cleanup"ed
>
> a simple cp, with subsequent svn add for the target (instead of svn
> cp) and eventually svn del in the source (instead of svn mv) works,
> but this workaround seems like subversion 1.2 - or worse.

Does anything in the error message pertain to your setup? IOW, do you
have other processes running that may be locking the file (antivirus
is notorious for this)? Is it a local filesystem, or mounted from the
network? If local, what filesystem are you using? If it's on the
network, have you taken the step suggested by the message?