Marc Haisenko <haisenko@webport.de> writes:
> Well, I finally managed to rescue my repository, thank you all for you
> help !
>
> What I did was a normal dump up to the corrupt revision, an
> incremental dump just after the corrup revision, create a new
> repository, load the first dump, check out the repository, add the
> files from the corrupt revision (luckily I have a commit hook that
> sends e-mails to me and luckily I have all of them) and then load the
> incremental dump.
>
> I guess this only worked so well because the files that were added in
> the corrupt revision were never changed afterwards... one of them was
> deleted in a later revision, but this was no problem.
Did you ever find out the cause of the corruption, though?
The words "data corruption" make us very nervous. When it turns out
to be bad RAM, we breathe a sigh of relief (though it would still be
nice if Subversion had some way to be more graceful about handling
such situations!).
However, if it wasn't bad RAM, the possibility exists that it was
Subversion itself...
Any new information?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 17 17:40:18 2004