[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: Phil Cairns <phil_at_pagaros.com.au>
Date: Sun, 8 Nov 2009 14:38:23 -0800 (PST)

> 2009/10/23 Sakshi Kaul <Sakshi.Kaul_at_kpitcummins.com>
> >
> > Hi,
> >
> > We are using SVN for Configuration Management and one of our project team is facing an issue while committing to SVN.
> >
> > Issue: DATABASE DISK IMAGE MALFORMED

[snip]

> I have done some search on what other SQLite users do in such a
> case (not Subversion users, but those, who use the SQLite database directly).

[snip]

> Thus the only way is to create a new subversion repository and restore
> it from your backups.
>
> Even if you do not have backups, I think that the current repository
> is still readable. You can try to create a copy of it, using svnadmin
> dump + load, or svnsync. See the SVN Book for details.

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.

Regards,
Phil.

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-09 00:15:10 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.