You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by bt c <cb...@yahoo.com> on 2005/10/29 07:31:52 UTC
svnadmin: Checksum mismatch while reading representation:
Hi,
My fsfs repository revision is now at 157.
C:\data\subversion>svnadmin dump -r 62:64 repo > temp.dmp
* Dumped revision 62.
svnadmin: Checksum mismatch while reading representation:
expected: 88abc4785b8dff25f78f90ba88515817
actual: 288b3be45d03427690dcad3880bb3dc1
As can be seen, revision 63 is problematic. So I try to recall roughly which are the files that are committed in revision 63, and when I try to check out those files for revision 63, as expected, the checksum error message appears again.
Ok, now how should I tackle this issue? Manually skip 63 everytime I want to backup?
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
Re: svnadmin: Checksum mismatch while reading representation:
Posted by John Szakmeister <jo...@szakmeister.net>.
On Monday 31 October 2005 19:43, Joshua Varner wrote:
> On 10/29/05, John Szakmeister <jo...@szakmeister.net> wrote:
> > On Saturday 29 October 2005 13:29, bt c wrote:
> > > Ok, what I just did was:
> > >
> > > svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
> > > svnadmin dump repo -r64:157 --incremental > repo_64to157.dmp
> > > // Rename repo to something else.
> > > svnadmin create repo
> > >
> > > svnadmin load repo < repo_1to62.dmp
> > >
> > > svnadmin load repo < repo_64to157.dmp
> > >
> > >
> > >
> > > My understanding is that I will not know what are the changes from 62
> > > to 63 now. Instead I am seeing only changes from 62 to 64 now.
> >
> > Correct. Don't forget to get a whole new WC though. Since the version
> > numbers changed, you're old working copy is now out of kilter with what
> > is actually in the repository.
>
> This may or may not work. Because you did an incremental dump at revision
> 64, the base that those diffs assume is the repository at revision 63.
> So changes to those files may not apply cleanly to the copy of the file
> that existed at revision 62.
Good catch! I completely missed the '--incremental' in there. The best way
would've been to use a full dump.
> Did you try to dump or svnadmin verify the new repository. It may work if
> the changes are small enough in rev 63 or just happen to work out that the
> diffs still apply, but you might want to check rev 64 to make sure it is
> clean.
>
> You could try this
> svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
> svnadmin dump repo -r65:157 --incremental > repo_65to157.dmp
>
> // get a working copy that was valid from a revision after 63 and
> // reverse merge back to 64 - call this wc64
>
> // Rename repo to something else.
>
> svnadmin create repo
> svnadmin load repo < repo_1to62.dmp
>
> // check out the repo, then copy over changes from wc64
> svn commit -m "Bridge gap" wc64
>
> svnadmin load repo < repo_65to157.dmp
>
> This way you don't have any holes. I doubt you could do a non-incremental
> dump b/c of the corruption. But if you are not having any problems, you
> may have been lucky enough that revision 63 was small or happened to be
> something that caused no problems.
I suspect this was the case.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnadmin: Checksum mismatch while reading representation:
Posted by Joshua Varner <jl...@gmail.com>.
On 10/29/05, John Szakmeister <jo...@szakmeister.net> wrote:
> On Saturday 29 October 2005 13:29, bt c wrote:
> > Ok, what I just did was:
> >
> > svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
> > svnadmin dump repo -r64:157 --incremental > repo_64to157.dmp
> > // Rename repo to something else.
> > svnadmin create repo
> >
> > svnadmin load repo < repo_1to62.dmp
> >
> > svnadmin load repo < repo_64to157.dmp
> >
> >
> >
> > My understanding is that I will not know what are the changes from 62 to 63
> > now. Instead I am seeing only changes from 62 to 64 now.
>
> Correct. Don't forget to get a whole new WC though. Since the version
> numbers changed, you're old working copy is now out of kilter with what is
> actually in the repository.
>
This may or may not work. Because you did an incremental dump at revision
64, the base that those diffs assume is the repository at revision 63.
So changes to those files may not apply cleanly to the copy of the file
that existed at revision 62.
Did you try to dump or svnadmin verify the new repository. It may work if the
changes are small enough in rev 63 or just happen to work out that the
diffs still apply, but you might want to check rev 64 to make sure it is clean.
You could try this
svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
svnadmin dump repo -r65:157 --incremental > repo_65to157.dmp
// get a working copy that was valid from a revision after 63 and
// reverse merge back to 64 - call this wc64
// Rename repo to something else.
svnadmin create repo
svnadmin load repo < repo_1to62.dmp
// check out the repo, then copy over changes from wc64
svn commit -m "Bridge gap" wc64
svnadmin load repo < repo_65to157.dmp
This way you don't have any holes. I doubt you could do a non-incremental
dump b/c of the corruption. But if you are not having any problems, you
may have been lucky enough that revision 63 was small or happened to be
something that caused no problems.
Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnadmin: Checksum mismatch while reading representation:
Posted by John Szakmeister <jo...@szakmeister.net>.
On Saturday 29 October 2005 13:29, bt c wrote:
> Ok, what I just did was:
>
> svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
> svnadmin dump repo -r64:157 --incremental > repo_64to157.dmp
> // Rename repo to something else.
> svnadmin create repo
>
> svnadmin load repo < repo_1to62.dmp
>
> svnadmin load repo < repo_64to157.dmp
>
>
>
> My understanding is that I will not know what are the changes from 62 to 63
> now. Instead I am seeing only changes from 62 to 64 now.
Correct. Don't forget to get a whole new WC though. Since the version
numbers changed, you're old working copy is now out of kilter with what is
actually in the repository.
> John, I appreciate your offer to help. As I am focusing my efforts on some
> other developments and do not wish to be sidetracked, and also that I can
> afford to lose the changes, I decide to go ahead with the quick solution.
> Maybe you can list out the steps that you will take in addressing this
> problem here?
It can be a bit tedious. In order to let the checkout proceed, we would have
needed to identify the problem file (which should've been in the error
message for your checkout). The we could've opened revision 63 in a hex
editior (repos/db/revs), found the appropriate representation for the file,
and changed the md5sum to all 0's (all 0's is our wildcard value for the
checksum... it matches everything). After that, you should've been able to
checkout again. The only question would have been whether the data in r63
was valid.
Hope that helps.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnadmin: Checksum mismatch while reading representation:
Posted by bt c <cb...@yahoo.com>.
Ok, what I just did was:
svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
svnadmin dump repo -r64:157 --incremental > repo_64to157.dmp
// Rename repo to something else.
svnadmin create repo
svnadmin load repo < repo_1to62.dmp
svnadmin load repo < repo_64to157.dmp
My understanding is that I will not know what are the changes from 62 to 63 now. Instead I am seeing only changes from 62 to 64 now.
John, I appreciate your offer to help. As I am focusing my efforts on some other developments and do not wish to be sidetracked, and also that I can afford to lose the changes, I decide to go ahead with the quick solution. Maybe you can list out the steps that you will take in addressing this problem here?
Thanks.
John Szakmeister <jo...@szakmeister.net> wrote:
On Saturday 29 October 2005 03:31, bt c wrote:
> Hi,
>
>
>
> My fsfs repository revision is now at 157.
>
>
>
> C:\data\subversion>svnadmin dump -r 62:64 repo > temp.dmp
>
> * Dumped revision 62.
>
> svnadmin: Checksum mismatch while reading representation:
>
> expected: 88abc4785b8dff25f78f90ba88515817
>
> actual: 288b3be45d03427690dcad3880bb3dc1
>
>
>
> As can be seen, revision 63 is problematic. So I try to recall roughly
> which are the files that are committed in revision 63, and when I try to
> check out those files for revision 63, as expected, the checksum error
> message appears again.
>
>
>
> Ok, now how should I tackle this issue? Manually skip 63 everytime I want
> to backup?
If you put a tarball up on the web somewhere and send me the URL (privately),
I'll fix it so that you can at least do the checkout and the dump. I'll need
your help in verifying the contents are correct though.
-John
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
Re: svnadmin: Checksum mismatch while reading representation:
Posted by John Szakmeister <jo...@szakmeister.net>.
On Saturday 29 October 2005 03:31, bt c wrote:
> Hi,
>
>
>
> My fsfs repository revision is now at 157.
>
>
>
> C:\data\subversion>svnadmin dump -r 62:64 repo > temp.dmp
>
> * Dumped revision 62.
>
> svnadmin: Checksum mismatch while reading representation:
>
> expected: 88abc4785b8dff25f78f90ba88515817
>
> actual: 288b3be45d03427690dcad3880bb3dc1
>
>
>
> As can be seen, revision 63 is problematic. So I try to recall roughly
> which are the files that are committed in revision 63, and when I try to
> check out those files for revision 63, as expected, the checksum error
> message appears again.
>
>
>
> Ok, now how should I tackle this issue? Manually skip 63 everytime I want
> to backup?
If you put a tarball up on the web somewhere and send me the URL (privately),
I'll fix it so that you can at least do the checkout and the dump. I'll need
your help in verifying the contents are correct though.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org