[svk-users] What to do when a db/revs/nnn file is sitting on a bad sector (success)

[David Landgren]

Jared Hardy wrote:
>> Jared Hardy wrote:
>>>     One hacky way around this might be to mirror a new .svk repository
>>> from your old one, and use "svk sync --torev 1576 ..." to stop it
> 
> On 10/14/07, David Landgren <david at landgren.net> wrote:
>> Umm, how exactly do I do this? Bearing in mind that I mirror a number of
>> different remote repos. As luck would have it, the lost revisions belong
>> to a single repo.
>> svk depotmap --list says that depot // has a path of /home/david/.svk/local
> 
> Maybe try something like this (don't take my word verbatim -- I
> haven't tested this):
> 
> mv /home/david/.svk/local /home/david/local-bad
> 
> svk depotmap --init /home/david/.svk/local
> # OR                  (-- not sure which works best here)
> svnadmin create /home/david/.svk/local
> 
> svnadmin dump -r 0:1576 file:///home/david/local-bad > local-bad.dump
> svnadmin load --force-uuid /home/david/.svk/local < local-bad.dump

Victory! Something very close to this is what worked. I added the recipe 
to the wiki.

   http://svk.bestpractical.com/view/SVKRebuildRepo

Thanks, I owe you a beer,
David