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

Re: sqlite database errors through vm share

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 19 Dec 2012 10:43:07 -0500

On Wed, Dec 19, 2012 at 10:31 AM, Michael D. Hoyle <hoylemd_at_gmail.com>wrote:

> Hey all,
> I'm running an ubuntu vm on VMware player on a Windows 7 machine. I have
> to have my code available on Windows for debugging (Microsoft server
> stuff), but I prefer to code in linux. My solution so far has been the VM
> with a shared directory pointing at my svn repo on the windows hard drive.
> The problem is that every 5 or 6 commits, the whole repo gets locked and
> any operation I try to execute (even cleanup) results in two E200030:
> sqlite: database disk image is malformed errors. So far, the only recovery
> for this I've found is to check out the repository anew, which takes a long
> time.
> Are there any easier ways to do what i'm trying to do? If not, is there a
> quicker way to recover from this?
Is it your repository that's locked, or your working copy?

Standard answer: Working copies should never be shared across OSes, and
repositories can only safely be shared by using a dedicated Subversion
server process (svnserve or Apache), never file:/// access via a file
share. Network file access schemes, as well as differences between OSes and
library versions used by the various clients, can cause havoc.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-12-19 16:43:53 CET

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

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