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

Re: Perforce checksum mismatch error while importing in svn

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Mon, 23 Sep 2019 20:31:54 -0400

> On Sep 23, 2019, at 8:35 AM, Stefan Sperling <stsp_at_elego.de> wrote:
>> 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.

That was a VisualSVN error screen. If the Windows GUI based toolkit is working against you, or your embedded Subversion is out of date, you might try Cygwin or TortoiseSVN published up-to-date Subversion and compare results.
Received on 2019-09-24 02:32:07 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.