You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Richard Jelinek <rj...@petamem.com> on 2014/06/13 15:28:29 UTC
svn mv and svn cp fails in 1.8.8 and 1.8.9
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.
for reference
-----------------------------------------------------------
# svn --version
svn, version 1.8.9 (r1591380)
compiled Jun 13 2014, 14:35:55 on x86_64-pc-linux-gnu
Copyright (C) 2014 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/
The following repository access (RA) modules are available:
* ra_svn : Module for accessing a repository using the svn network
protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol
using serf.
- using serf 1.3.4
- handles 'http' scheme
- handles 'https' scheme
-----------------------------------------------------------
kind regards,
--
Dipl.-Inf. Univ. Richard C. Jelinek
PetaMem GmbH - www.petamem.com Geschäftsführer: Richard Jelinek
Language Technology - We Mean IT! Sitz der Gesellschaft: Fürth
2.58921 * 10^8 Mind Units Registergericht: AG Fürth, HRB-9201
Re: svn mv and svn cp fails in 1.8.8 and 1.8.9
Posted by Richard Jelinek <rj...@petamem.com>.
On Fri, Jun 13, 2014 at 06:17:23PM +0000, Bert Huijben wrote:
> Are there any symlinks involved in these paths that you passed to Subversion?
Now THAT is a very interesting question. Actually there are, and when
I use paths that do not contain any parts which are symlinks, all
works! Thanks for solving the mystery.
Now I am only afraid, that someone will tell me this is a feature and
not a bug. :-)
kind regards,
--
Dipl.-Inf. Univ. Richard C. Jelinek
PetaMem GmbH - www.petamem.com Geschäftsführer: Richard Jelinek
Language Technology - We Mean IT! Sitz der Gesellschaft: Fürth
2.58921 * 10^8 Mind Units Registergericht: AG Fürth, HRB-9201
Re: svn mv and svn cp fails in 1.8.8 and 1.8.9
Posted by Bert Huijben <be...@qqmail.nl>.
Are there any symlinks involved in these paths that you passed to Subversion?
Bert
Sent from Windows Mail
From: Richard Jelinek
Sent: Friday, June 13, 2014 4:45 PM
To: Andy Levy
Cc: users@subversion.apache.org
Hi,
On Fri, Jun 13, 2014 at 09:41:27AM -0400, Andy Levy wrote:
> 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?
* no other (relevant) process
* local filesystem (ext4)
* did definitely work with 1.6 and 1.7
Only thing I can offer: The repository in question has a very
extensive directory structure. Imagine ISO639-3 codes stored as tries
of directories with subdirectories. The repository contains roughly
19000 directories/files. But then again this is nothing extraordinary
big, is it?
From the observation, it seems like subversion runs into some kind of
timeout AFTER it has locked the destination directory.
But the sandbox is on a quite fast ssd and there is neither cpu nor
disc activity, which would indicate it is a processing-induced
timeout.
regards,
--
Dipl.-Inf. Univ. Richard C. Jelinek
PetaMem GmbH - www.petamem.com Geschäftsführer: Richard Jelinek
Language Technology - We Mean IT! Sitz der Gesellschaft: Fürth
2.58921 * 10^8 Mind Units Registergericht: AG Fürth, HRB-9201
Re: svn mv and svn cp fails in 1.8.8 and 1.8.9
Posted by Richard Jelinek <rj...@petamem.com>.
Hi,
On Fri, Jun 13, 2014 at 09:41:27AM -0400, Andy Levy wrote:
> 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?
* no other (relevant) process
* local filesystem (ext4)
* did definitely work with 1.6 and 1.7
Only thing I can offer: The repository in question has a very
extensive directory structure. Imagine ISO639-3 codes stored as tries
of directories with subdirectories. The repository contains roughly
19000 directories/files. But then again this is nothing extraordinary
big, is it?
>From the observation, it seems like subversion runs into some kind of
timeout AFTER it has locked the destination directory.
But the sandbox is on a quite fast ssd and there is neither cpu nor
disc activity, which would indicate it is a processing-induced
timeout.
regards,
--
Dipl.-Inf. Univ. Richard C. Jelinek
PetaMem GmbH - www.petamem.com Geschäftsführer: Richard Jelinek
Language Technology - We Mean IT! Sitz der Gesellschaft: Fürth
2.58921 * 10^8 Mind Units Registergericht: AG Fürth, HRB-9201
Re: svn mv and svn cp fails in 1.8.8 and 1.8.9
Posted by Andy Levy <an...@gmail.com>.
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?