You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mike Craig <Mi...@freeclear.com> on 2007/03/07 21:18:00 UTC

Failure creating dump file

I have tried a couple of times to create a dump file to convert from SVN
1.3.0 to 1.4.3, however I keep getting Checksum errors. There are a few
revisions with large Binary check-ins, and I believe this is what is
making SVNDUMP choke.

I have tried the following Commands from both the 1.3.0 and 1.4.3
svnadmin versions:
	svnadmin dump --deltas
e:\svn_repository>e:\svn_export\deltas.dmp
	svnadmin dump e:\svn_repository>e:\svn_export\svn_repos.dmp

Output from svndump command:
	* Dumped revision 5511.
	svnadmin: Checksum mismatch while reading representation:
   	expected:  46a85a0e6f0606cd517bcc032a9758f1
     	actual:  37c2083234feb464f16a44eb4aedb5b6

Mike Craig

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: Failure creating dump file

Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
Mike Craig wrote:
> Disregard my small size amount, this revision is over 1GB in size.

...but we all know size doesn't matter. ;)
Seriously, I do think that Subversion should be able to handle such commit 
sizes or at least fail with an error, but I can't comment on that since I 
only version source code.

> As for 'the broken revision from a backup', we perform the hotcopy and back
> up the hotcopy. How can I take a specific revision from the backup and
> insert it into my 'broken' copy at the same revision?

The first thing you need to do is find a backup where you can 'svnadmin dump' 
that very revision. Then you load the content up to and including that 
revision into a new repository and take the rest from the live repository. 
You will need a switch telling the dump command to perform the later dump 
only incrementally.

BTW: I wouldn't backup the hotcopy. The point is that the format of the 
repository is platform-dependant (well, at least the BDB one is), while the 
format of the dumpfile is explicitly intended to be compatible. Our backup 
here is to first hotcopy the repository and then perform a dump on the 
hotcopy and move that to a different machine where it's backed up. The 
hotcopies remain on the server, because they also contain things like 
svnserve configuration and hook scripts, which are not contained in the 
dumpfile and to have a hot spare.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH
Geschäftsführer: Ronald Boers       Steuernummer: 02/892/02900 
Amtsgericht Hamburg HR B62 932      USt-Id.Nr.: DE183047360

**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.

**************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


RE: RE: Re: Failure creating dump file

Posted by Mike Craig <Mi...@freeclear.com>.
Disregard my small size amount, this revision is over 1GB in size.

-----Original Message-----
From: Mike Craig [mailto:Mike.Craig@freeclear.com] 
Sent: Thursday, March 08, 2007 10:51 AM
To: users@subversion.tigris.org
Subject: RE: Re: Failure creating dump file

I examined the files in this revision, and I was wrong, they are standard aspx files. Our repository does have several zip files in the 50-80MB range.

As for 'the broken revision from a backup', we perform the hotcopy and back up the hotcopy. How can I take a specific revision from the backup and insert it into my 'broken' copy at the same revision? 

Thank you for the reply.

Mike


-----Original Message-----
From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com] 
Sent: Thursday, March 08, 2007 12:24 AM
To: users@subversion.tigris.org
Subject: Re: Failure creating dump file

On Wednesday 07 March 2007 22:18, Mike Craig wrote:
> I have tried a couple of times to create a dump file to convert from SVN
> 1.3.0 to 1.4.3, however I keep getting Checksum errors. There are a few
> revisions with large Binary check-ins, and I believe this is what is
> making SVNDUMP choke.

Define 'large'. Other than that, all check-ins are binary ;).

> I have tried the following Commands from both the 1.3.0 and 1.4.3
> svnadmin versions:
> 	svnadmin dump --deltas
> e:\svn_repository>e:\svn_export\deltas.dmp
> 	svnadmin dump e:\svn_repository>e:\svn_export\svn_repos.dmp
>
> Output from svndump command:
> 	* Dumped revision 5511.
> 	svnadmin: Checksum mismatch while reading representation:
>    	expected:  46a85a0e6f0606cd517bcc032a9758f1
>      	actual:  37c2083234feb464f16a44eb4aedb5b6

Typically, this is a sign of some repository corruption. The normal way to fix 
that is to just take the broken revision from a backup.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH
Geschäftsführer: Ronald Boers       Steuernummer: 02/892/02900 
Amtsgericht Hamburg HR B62 932      USt-Id.Nr.: DE183047360

**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.

**************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


RE: Re: Failure creating dump file

Posted by Mike Craig <Mi...@freeclear.com>.
I examined the files in this revision, and I was wrong, they are standard aspx files. Our repository does have several zip files in the 50-80MB range.

As for 'the broken revision from a backup', we perform the hotcopy and back up the hotcopy. How can I take a specific revision from the backup and insert it into my 'broken' copy at the same revision? 

Thank you for the reply.

Mike


-----Original Message-----
From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com] 
Sent: Thursday, March 08, 2007 12:24 AM
To: users@subversion.tigris.org
Subject: Re: Failure creating dump file

On Wednesday 07 March 2007 22:18, Mike Craig wrote:
> I have tried a couple of times to create a dump file to convert from SVN
> 1.3.0 to 1.4.3, however I keep getting Checksum errors. There are a few
> revisions with large Binary check-ins, and I believe this is what is
> making SVNDUMP choke.

Define 'large'. Other than that, all check-ins are binary ;).

> I have tried the following Commands from both the 1.3.0 and 1.4.3
> svnadmin versions:
> 	svnadmin dump --deltas
> e:\svn_repository>e:\svn_export\deltas.dmp
> 	svnadmin dump e:\svn_repository>e:\svn_export\svn_repos.dmp
>
> Output from svndump command:
> 	* Dumped revision 5511.
> 	svnadmin: Checksum mismatch while reading representation:
>    	expected:  46a85a0e6f0606cd517bcc032a9758f1
>      	actual:  37c2083234feb464f16a44eb4aedb5b6

Typically, this is a sign of some repository corruption. The normal way to fix 
that is to just take the broken revision from a backup.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH
Geschäftsführer: Ronald Boers       Steuernummer: 02/892/02900 
Amtsgericht Hamburg HR B62 932      USt-Id.Nr.: DE183047360

**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.

**************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: Failure creating dump file

Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Wednesday 07 March 2007 22:18, Mike Craig wrote:
> I have tried a couple of times to create a dump file to convert from SVN
> 1.3.0 to 1.4.3, however I keep getting Checksum errors. There are a few
> revisions with large Binary check-ins, and I believe this is what is
> making SVNDUMP choke.

Define 'large'. Other than that, all check-ins are binary ;).

> I have tried the following Commands from both the 1.3.0 and 1.4.3
> svnadmin versions:
> 	svnadmin dump --deltas
> e:\svn_repository>e:\svn_export\deltas.dmp
> 	svnadmin dump e:\svn_repository>e:\svn_export\svn_repos.dmp
>
> Output from svndump command:
> 	* Dumped revision 5511.
> 	svnadmin: Checksum mismatch while reading representation:
>    	expected:  46a85a0e6f0606cd517bcc032a9758f1
>      	actual:  37c2083234feb464f16a44eb4aedb5b6

Typically, this is a sign of some repository corruption. The normal way to fix 
that is to just take the broken revision from a backup.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH
Geschäftsführer: Ronald Boers       Steuernummer: 02/892/02900 
Amtsgericht Hamburg HR B62 932      USt-Id.Nr.: DE183047360

**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.

**************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org