Re: [p4] Corrupted during transfer
Matt Janulewicz <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'Matt Janulewicz'. It's an outside chance, but this smells a tiny bit like this bug that was fixed in 2017.2: #1525293 (Bug #90697) ** Parallel submit from an Edge Server could corrupt the archives of non-ktext files if they contain RCS keywords. This has been fixed. The nature of it was the we were submitting certain windows binaries that happened to have the character sequence "$Version$" in the metadata. The server was finding this and munging it. The difference here is that in our case the submit would go through on the first try but you'd get weird failures when syncing. Our workaround was to disable parallel submit using a trigger (haven't upgraded yet.) Are you in a commit->edge architecture, running a server older than 2017.2 and using parallel submit? If not, ignore message. :) If so, perhaps disable parallel submit explicitly on your next submit and see what happens. Even though your submit eventually succeeds, I'd be weary that it's actually correct. It might be fun to p4 verify the last revision and compare it to the locally run md5sum to see if they're the same. BTW, we probably have files submitted that are bigger than 60 MB every day, often much larger (1 GB or more.) Until we ran into this bug we've never had a problem with bigger binary files. -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5560-corrupted-during-transfer _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user