Perforce Public Knowledge Base - Replication log reports file "corrupted during transfer"
Reset Search
 

 

Article

Replication log reports file "corrupted during transfer"

« Go Back

Information

 
Problem

Your replication log reports a server error that a file was corrupted during transfer.

Perforce server error:
    2011/04/07 11:29:57 pid 2812 qbrown@21112 background 'pull -u -i 5'
    depot/TestFolder/tester corrupted during transfer B1DCB1A752668E27DB5DD795DCB8A8F1 vs
 C9273CAA9E1286A8A0DFC3F68F02A6C2

This means the calculated checksum on the replica (the first value given) does not match the checksum received from the master.  For this example, the master checksum of C9273CAA9E1286A8A0DFC3F68F02A6C2 does not match the received revision's checksum of B1DCB1A752668E27DB5DD795DCB8A8F1

Solution

PROBLEM

Your replication log reports a server error that a file was corrupted during transfer.

Perforce server error:
    2011/04/07 11:29:57 pid 2812 qbrown@21112 background 'pull -u -i 5'
    depot/TestFolder/tester corrupted during transfer B1DCB1A752668E27DB5DD795DCB8A8F1 vs
 C9273CAA9E1286A8A0DFC3F68F02A6C2

This means the calculated checksum on the replica (the first value given) does not match the checksum received from the master.  For this example, the master checksum of C9273CAA9E1286A8A0DFC3F68F02A6C2 does not match the received revision's checksum of B1DCB1A752668E27DB5DD795DCB8A8F1

DETAILS

There are known causes:

  1. The file revision was corrupted during transfer.
  2. The file revision is corrupt on the master server. 
  3. ktext files containing keywords that may differ on the master vs replica.  For example, a $Date value where the two servers are in different timezones
  4. Shelved files that are updated before the first shelved file was transferred.

Action Steps

The transfer will be attempted repeatedly, so first determine if the error occurs once, or a few times, but then stops occurring.

If the message is transient, the likely cause is a transfer issue.  Investigate any possible network or OS related causes.

If the error persists, perform a "p4 verify" on the master file.

For example:

$ p4 -p <masterHost>:<port> verify //depot/TestFolder/tester
//depot/TestFolder/tester#3 - edit change 45 (text) C9273CAA9E1286A8A0DFC3F68F02A6C2 BAD!
//depot/TestFolder/tester#2 - edit change 44 (text) 6A7C3AA0D7C68066281BB0A09DA019D0
//depot/TestFolder/tester#1 - add change 41 (text) 2A07077A7E400292F8A60F8477EF0970

Note:  A 'p4 -p  pull -l' should also show the problem file revision.  See "1.45" in this example:

$ p4 <replicaHost>:<port> pull -l
//depot/TestFolder/tester 1.45 text error edit B1DCB1A752668E27DB5DD795DCB8A8F1 11 740
2011/04/07 11:59:37
15 depot/testfolder/tester corrupted during transfer B1DCB1A752668E27DB5DD795DCB8A8F1
vs C9273CAA9E1286A8A0DFC3F68F02A6C2

Fixing the Archive File

If the problem is determined to be a problem with the master archive file, please refer to the the KB article How to Handle p4 verify BAD Errors .

Once the BAD error is fixed, the file replication will succeed.

If the replication does not proceed, please contact Perforce Technical Support.

Other Situations

If none of the above steps explain your situation please contact Perforce Technical Support.

Related Links

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255