subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Santosh Kondapuram <SKondapu...@vitechinc.com>
Subject RE: Issue while loading the SVN Dump SVN version 1.9.7
Date Thu, 25 Jan 2018 09:40:03 GMT
Hi Johan,

I have tried reloading the dump as you suggested with  -M 0 option but still I am running
in to the same issue.
Seems like the svn admin could not load the dump due to sha1 collision files. So the question
is how do I identify the sha1 colliding files ? does the error stack trace say something about
it ?
 As per the sha1-advisory note if we create a Subversion permission rule(authz) that block
access to the one or both of the files, then tools like svnsync will not send the colliding
content.
So If someone can help me in identifying the colliding files then I would like to block them
and sync my mirror repository. Below is the error I am hitting.
Any help much appreciated and I am very much new to the subversion.

https://subversion.apache.org/security/sha1-advisory.txt

FYI,
svnadmin: E160000: SHA1 of reps '669684 7 1143 195972 efbdb058ce857b2860cfa245f014f0b9 9db457be74545c184242e57208bf1d56db1f15b2
724412-fiyk/_16' and '-1 0 929 195972 efbdb058ce857b2860cfa245f014f0b9 9db457be74545c184242e57208bf1d56db1f15b2
724412-fiyk/_16' matches (9db457be74545c184242e57208bf1d56db1f15b2) but contents differ
svnadmin: E160004: Filesystem is corrupt
svnadmin: E200014: Checksum mismatch while reading representation:
   expected:  efbdb058ce857b2860cfa245f014f0b9
     actual:  04a53277f405bcbab8a3b1fff9f8c6e0

Thanks,
Santosh.

-----Original Message-----
From: Johan Corveleyn [mailto:jcorvel@gmail.com] 
Sent: Monday, January 22, 2018 5:50 PM
To: Santosh Kondapuram <SKondapuram@vitechinc.com>
Cc: users@subversion.apache.org
Subject: Re: Issue while loading the SVN Dump SVN version 1.9.7

On Thu, Jan 18, 2018 at 1:34 PM, Santosh Kondapuram <SKonudapuram@vitechinc.com> wrote:
> HI All,
>
>
>
> I am running in to issues while loading the SVN dump to one of the 
> newly created SVN repository and the error happens only while loading 
> specific revision 724413.
>
> Please find the error message below. Appreciate your help !!
>
> Source SVN version : 1.9.5
>
> Target SVN version : 1.9.7
>
>
>
>
>
> FYI,
>
>
>
> [root@vitech-svn-slave-test-01 svndump]# svnadmin load /u01/svn/repos 
> < incdump_724413.txt
>
> <<< Started new transaction, based on original revision 724413
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/Scripts/DML_Exception
> /web_dml_admin_businessEntityRelationsHistory.sql
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/Scripts/DML_Exception
> /web_dml_admin_securityApplicationUserHistory.sql
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/Scripts/DML_Exception
> /web_dml_admin_securityRoleUserHistory.sql
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/Scripts/DML_Exception
> /web_dml_admin_userMaintenance_audit_Labels.sql
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/BusinessEntityRelationHist.hbm
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/BusinessEntityRelationHist.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/SecurityApplicationUsrHist.hbm
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/SecurityApplicationUsrHist.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/SecurityRoleUserHist.hbm
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/SecurityRoleUserHist.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/base/BaseBusinessEntityRelationHist.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/base/BaseSecurityApplicationUsrHist.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/model/base/BaseSecurityRoleUserHist.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/services/SecurityService.java
> ... done.
>
>      * editing path :
> v3-web-product/branches/8.3.0.279_IPERS/benefits/src/com/vitechinc/v3/
> admin/services/SecurityServiceImpl.java
> ...svnadmin: E160000: SHA1 of reps '669684 7 1143 195972
> efbdb058ce857b2860cfa245f014f0b9 
> 9db457be74545c184242e57208bf1d56db1f15b2
> 724412-fiyk/_16' and '-1 0 929 195972 efbdb058ce857b2860cfa245f014f0b9
> 9db457be74545c184242e57208bf1d56db1f15b2 724412-fiyk/_16' matches
> (9db457be74545c184242e57208bf1d56db1f15b2) but contents differ
>
> svnadmin: E160004: Filesystem is corrupt
>
> svnadmin: E200014: Checksum mismatch while reading representation:
>
>    expected:  efbdb058ce857b2860cfa245f014f0b9
>
>      actual:  04a53277f405bcbab8a3b1fff9f8c6e0
>

Hello,

This looks similar to this problem (which was present in 1.8.19, but probably the same bug
is still present in 1.9.7):

http://mail-archives.apache.org/mod_mbox/subversion-users/201707.mbox/%3C5aae07a9-bb6d-6340-206a-dafcf91e35e6%40apache.org%3E

Performing the load with the option "-M 0" (disabling the in-memory cache during load, making
it a little bit slower) should work around it.

HTH,
--
Johan

This e-mail message and any files transmitted with it may contain confidential and proprietary
information and are intended solely for the use of the individual or entity to which they
are addressed. Any unauthorized review, use, disclosure or distribution is strictly prohibited.
If you have received this e-mail in error please notify the sender by reply email and destroy
all copies of the original message. Thank you for your cooperation.
Mime
View raw message