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

Re: Repository Corruption

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-08-15 23:46:07 CEST

Koffie Yahoo wrote:
> Hi,
> When I tried to commit to one of my repositories yesterday, the commit
> failed with a check sum error. After getting this error I (maybe stupid
> enough) ran svnadmin recover on the repository.
> I'm now getting the following errors (copy-n-paste from my prompt, where
> h:/dis_repro is the repository, where bla is an empty directory, and where
> dis2 holds a checkout copy from before the corruption):
> D:\work\bla>svn checkout file:///h:/dis_repro
> svn: No transaction named '30' in filesystem 'h:/dis_repro/db'
> D:\work\dis2>svn update
> svn: No transaction named '30' in filesystem 'h:/dis_repro/db'
> D:\work\dis2>svn commit -m"bla"
> svn: Commit failed (details follow):
> svn: No transaction named '30' in filesystem 'h:/dis_repro/db'
> D:\work>svnadmin dump h:\dis_repro > bla.txt
> * Dumped revision 0.
> svn: No such string '8r'
> D:\work\dis2>svn diff -r39:40 > bla.txt
> svn: No such string '8r'
> Looking at bit further into this, all errors seem to be related to just
> one of the files in the repository, for all other I could just run svn
> diff
> to extract all revisions. So, my question is as follows: Is it in some
> way possible to salvage some (or all) of the revisions of the file
> which I'm having trouble with?

Somehow, some nasty corruption has occurred.
Salvage from this situation requires in-depth knowledge of the internal
format of the repository - if you can put a .zip file of the damaged
repository somewhere that I can download it, I will have a look and see what
I can do.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 15 23:46:43 2005

This is an archived mail posted to the Subversion Dev mailing list.

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