"Sommers, Elizabeth" <SommersE_at_Pragmatics.com> writes:
> The domain: a 37 gig subversion repository. revisions 0:183031
> subversion version 1.4.4 ubuntu linux OS
>
> The problem: We have a bad record at 85431. We need to get rid of this
> record so that we can use Fisheye.
When you say "bad record", what's the exact error message you're seeing,
and for what operations?
> Our attempted solution: split the dump at (A) 0:85420 (B) 85440:90000
> (Don't need the whole dump to test solutions).
>
> Outcomes of different attempts to load these archives.
>
> 1) Load A and then try to load B - get the error message svnadmin: File
> already exists: filesystem '/svn/lizTest/db', transaction '85420-1',
> path 'jserv_G4'
So perhaps somewhere between r85420 and r85440, 'jserv_G4' was removed,
and later another file added at that same path (or the original file
restored)? Does that match with your records?
> 2) Load B - get the error message svnadmin: Relative source revision
> -10 is not available in current repository
Yeah, I wouldn't expect loading B by itself to work -- it depends on too
much history created in A.
> Load exits on both of these error messages
>
> Query: How do I get around these error messages to get a decent dump?
>
> Added information. I have tried to do this with dumps that went from
> 0:85430 and 85432:90000, but they did not work in the exact same way for
> attempt #1. I dumped fewer records this time hoping that it was
> something to do with being related to the bad record.
Do you get the same result if you try 0:85430 and 85431:90000? (Note
the "1" instead of "2" at the end of "85431" this time.)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-22 19:05:49 CEST