[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [EXTERNAL] Re: Perforce checksum mismatch error while importing in svn

From: Kumar, Raushan <Raushan.Kumar_at_harman.com>
Date: Tue, 24 Sep 2019 06:34:29 +0000

Added Screen shot. ________________________________________ From: Kumar, Raushan Sent: 24 September 2019 11:48 To: Stefan Sperling; Branko Čibej Cc: users_at_subversion.apache.org; Dafe, Narendra; Shilp, Kumar; Kumar20, Mukesh Subject: Re: [EXTERNAL] Re: Perforce checksum mismatch error while importing in svn Hi Stefan, I have tried with latest version of svn that is 1.12.2.I have tried with svnadmin load -M 0 command also but still its throw the checksum mismatch error. I have attached the screen shot. please refer it. Regards, Raushan ________________________________________ From: Stefan Sperling <stsp_at_elego.de> Sent: 23 September 2019 18:05 To: Branko Čibej Cc: users_at_subversion.apache.org; Kumar, Raushan Subject: [EXTERNAL] Re: Perforce checksum mismatch error while importing in svn On Mon, Sep 23, 2019 at 01:53:58PM +0200, Branko Čibej wrote: > On 23.09.2019 13:20, Kumar, Raushan wrote: > > > > Hi Team, > > > > > > I created a perforce dump using p42svn perl script, it created > > successfully as showing in below screen. > > > > it is created successfully but while importing it on svn server > > showing checksum mismatch error, as showing in below screen. > > > > This is obviously a bug in the p42svn script. It's calculating the > checksums incorrectly, and there's not much Subversion can do after the > fact. > > Sure, we could add an option to 'svnadmin load' to ignore checksums in > the dump file, but IMO that would be a really silly thing to do, because > the purpose of those checksums is verifying data integrity, and without > that verification one might as well move the repository to /dev/null. > > You really should report this to the authors of the p42svn script. If using SVN 1.8, try using 'svnadmin load -M 0'. 1.8 has a caching bug in 'svnadmin load' which results in this kind of error. Setting the memory cache size to zero with the -M option works around it.

screen shot2.PNG
screen shot1.PNG
Received on 2019-09-24 08:35:08 CEST

This is an archived mail posted to the Subversion Users mailing list.