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

database corruption

From: Pejvan BEIGUI <pejvan_at_online.fr>
Date: 2004-07-16 03:17:48 CEST

Hi All,

I'm not an old time user of Subversion but I've been quite happy with it
for the last three months.

But since today, I've got a very weird issue : I'm unable to do anything
with it, from checkouts to committing, with the folliwing errors :

> _pejvan_ trunk >> svn commit -m "cleaned up code for release"
> svn: Commit failed (details follow):
> svn: Berkeley DB error while checkpointing after Berkeley DB transaction for filesystem /Users/pejvan/Safe/subversion-repository/db:
> Invalid argument
> Abort

> _pejvan_ subversion-repository >> svnadmin verify /Users/pejvan/Safe/subversion-repository
> svn: Berkeley DB error while checkpointing after Berkeley DB transaction for filesystem /Users/pejvan/Safe/subversion-repository/db:
> Invalid argument
> svn: Berkeley DB error while closing 'nodes' database for filesystem /Users/pejvan/Safe/subversion-repository/db:
> Invalid argument

Has my database all the sudden get corrupted? I really don't understand
anything about what could possibly gone wrong and I couldn't find
anything any answer after googling and digging the mailing list archives.

How can I fix that?
How can I get my database information back?

I'm just about to install subversion for a whole team of developers, and
this could be a terrible issue if it had happened to them. No I'm quite
afraid of using subversion :-!

Thanks for your help in recovering my data!

Pejvan

-- 
Pejvan BEIGUI                                     pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.

Received on Fri Jul 16 03:48:05 2004

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.