subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eiren Smith <eir...@gmail.com>
Subject Re: Recovering repository with multiple missing rev/ files
Date Wed, 04 Aug 2010 21:25:24 GMT
On Jul 30, 2010, at 6:41 PM, Stefan Sperling wrote:

> On Fri, Jul 30, 2010 at 03:43:12PM -0400, Eiren Smith wrote:
>> 2. Copied revision revs/7/7263 file from that dumpfile-backup-based repo into my
production repo (the one missing some revs/ files -- I'll call it my corrupt repo).
> 
> Copying rev files like this most likely won't work.
> 
>> 3. Tried to dump that corrupt repo to ensure that my transplanted 7263 file was well
received. Result:
>> 
>> ...
>> * Dumped revision 7262.
>> svnadmin: Corrupt node-revision '0-5919.0.r7252/272624'
>> svnadmin: Missing id field in node-rev
> 
> To replay changes you've lost, you need to pretend to be a developer
> making the changes again.
> You need to use svn checkout to get a working copy, make the changes
> which happened (and have been lost) in that working copy, and use
> svn commit to commit the changes, thereby re-creating the missing
> revision. Then load additional revisions on top using svnadmin load.
> 
> If you don't know exactly what changes were made in the lost revisions,
> maybe you can interpolate the changes by looking at past and
> future revisions around the time of the missing changes?
> 
> You were talking about changes made to binary files in
> http://svn.haxx.se/users/archive-2010-06/0218.shtml so it can be
> quite hard to recreate the changes.
> Maybe you can get away with just omitting the missing revisions
> entirely? Dump all revisions you are able to dump. For the first dump,
> use svnadmin dump -r0:X (where X is the last good revision before the
> first one that got broken by the disk failure). For any dump
> of later revision use svnadmind dump -rA:B with the --incremental option
> of svnadmin dump. Then try to load all the dumps in succession.
> 
> I'm not sure what you mean when you describe that loading a dump
> file into a repository causes a single large revision to be created.
> That doesn't make any sense to me. I've never seen this happen.
> When this happens, what's the output of the svnadmin load command,
> and what's the output of the svn log command? Maybe I'm misunderstanding
> what you are trying to say? Please show the exact command you are using
> for loading. In fact, it would really help if you could simply post a
> transcript of all the commands you have tried running so far, and their
> output, without explaining your interpretation of things. This should
> help avoid misunderstandings. Based on such a transcript, we could ask
> further questions and provide hints, and hopefully help you fix the problem.
> 
> Stefan

Thank you very much for all your help, Stefan.  My window of time in which to restore this
repository has passed now. So I'm going to restore my old backup and just lose the revisions
between then and now. I don't expect to lose any final file versions, so the version history
should be the only casualty.

/eiren


Mime
View raw message