You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Robert S. Sfeir" <yo...@gmail.com> on 2005/03/22 20:55:57 UTC

Revert to fix corrupted files in repository

While investigating possible repository corruption I ran the svnadmin  
utility and got the following:

...
* Verified revision 371.
* Verified revision 372.
* Verified revision 373.
* Verified revision 374.
* Verified revision 375.
Segmentation fault

We're currently at revision 481, so something happened way back and  
didn't seem to affect anything, but svnadmin is not helping tell us  
what the issue is, only that it got an exception and ate it.  No  
verbose mode it seems to see where the problem might be.

We're running FSFS not BDB.

So I tried checking out the 376 revision and the file causing this  
problem is called AttributeManagerImpl, the svnadmin util check won't  
get past it.  I know that because I tried to check out 377, and I got  
AttributeManagerImpl's diffs, I can also see the logs on those  
revisions, but there is a file after that one that is causing a  
problem as well in the next revision.  The next 378 revision seems to  
be OK so it's only in these 2 revisions.  It seems that I indeed have  
files in the repository which got somehow corrupted.  The files which  
have these issues are no longer in use in the current repository  
revisions, they were deleted at revision 477 (no I was not marking  
the 100 revision anniversary, complete fluke).

Is there any way I can somehow fix this corruption at 376-378?  I  
mean do I have ANY options to end up with a clean repository?  Losing  
information in those revisions is acceptable, if I can figure out a  
way to do that.  I am assuming that doing a dump is useless since  
this is what svnadmin does on verify, and It would end up failing on  
dump as well.

Thanks
R


Robert S. Sfeir
yosemitesam(at)gmailNOSPAM.com