All,
I have a co worker who started getting an error on a file in our
repository. The error is:
subversion/libsvn_wc/update_editor.c:1582: (apr_err=155017)
svn: Checksum mismatch for 'src/com/codepuccino/mesquite/web/
security/.svn/text-base/MesquiteAuthenticationDao.java.svn-base';
expected: '97d99fba017193a327b0f886eb9e535f', actual:
'96e904c5245213b320f1b1a1d28c4c25'
The problem is that I can edit this file and check in code to it no
problem. Removing the directory containing the code and updating,
updates the dir and he can check the file in. The question is how
does this happen in the first place.
So I went into the server and tried to run svnadmin verify repo and
it goes through and then does one of those:
...
* 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 repository won't get past
it. I know that because I tried to check out 377, and I got
AttributeManagerImpl, but there is a file after that one that is
causing a problem as well. So it seems that there are files in the
repository which somehow got corrupted. The files which have issues
are no longer in use in the repository, they were deleted around
version 470.
So questions are:
1- wth is this first error and how do we get around it.
2- What are our options with fixing the repository without losing
data? Obviously verify fails, and I know which file is the problem,
is there a safe way to repair that, even if it means losing the file
and its data?
Thanks
R
Robert S. Sfeir
yosemitesam(at)gmailNOSPAM.com
Received on Tue Mar 22 02:22:57 2005