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

Re: SVN Error:"Database Disk image is malformed"

From: Andy Levy <andy.levy_at_gmail.com>
Date: Sun, 8 Nov 2009 18:45:05 -0500

On Sun, Nov 8, 2009 at 17:38, Phil Cairns <phil_at_pagaros.com.au> wrote:
> I, too, have this problem, and I've been able to restore the repository to a correct state by dumping and reloading. However, this is getting painful as I'm only getting a couple of commits before the error arises again. It only started when I decided to upgrade to 1.6 of svn. Up until that point, I was running with 1.4 on my QNAP NAS.
>
> I figured that the problem may have been with the NAS (running svnserve -d), so I moved the server process from the NAS to my Windows development machine (using VisualSVN Server), and pointing that at the repository on the NAS (using a UNC path to the repository).
>
> I see this problem whether I'm using VisualSVN from within Visual Studio, TortoiseSVN from the Explorer, or svn directly from a Cygwin command line.
>
> It looks like this:
> $ svn ci ftpbackup/syncremote.py
> Sending        ftpbackup/syncremote.py
> Transmitting file data .svn: Commit failed (details follow):
> svn: database disk image is malformed
> svn: Your commit message was left in a temporary file:
> svn:    '/cygdrive/d/Projects05/MVP2/ftpbackup/svn-commit.tmp'
>
> I'd have to regard this as a server problem, not a client problem.
>
> I guess the next thing to do is to try and keep the repository on my windows machine and make backups to the NAS, but I'm not keen on this. I'm going research git over the next couple of days, and if the problem persists, see if it's worth switching.

I think when you move from the NAS to keeping the repository on the
Windows box, you'll see the problem disappear. Accessing repositories
over shares is known to be a problem due to how locking and other
mechanisms operate on some network filesharing protocols (and even
certain versions of those protocols, or certain configurations of
them).

The advice generally is "don't do that" - it's not really a supported
configuration. Keep your repository local to the server process
itself.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2415637

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-09 00:45:58 CET

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.