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

Phoney revisions (was: Repository "hung")

From: Peter Howard <pjh_at_coastal.net.au>
Date: 2003-01-13 04:53:32 CET

I've given up on the existing repository, started a new one and loaded in
the old dump then committing my working copy over the top. During the
process I made the following discoveries

- svnadmin dump actually made it (with both svn and db built in debug) up to
revision 109.
- Going back through the log files (and cross checking against my memory as
to what I had been doing back on Jan 6 when it died) I discovered that
revision 109 was either the very last or second last revision that I had
committed before the repository went ga-ga. The log files for revisions
110/111-165 do not correspond to any real checkins.

So I've kept nearly all/all of my work (yay!). But where the fsck did those
other log files come from. I'm now running svn 0.16.1 and db4.1.24 (hit the
problem with 0.15 and db4.0.14) and hoping it never reappears.

This is now just information in case anyone else hits something similar.


(PS - I too have noticed the slowdown going from db 4.0 to 4.1 - but as I'm
feeling slightly paranoid about database integrity right now I'm living with

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 13 04:54:19 2003

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.