Re: [p4] Corrupted during transfer

Posted on behalf of forum user 'Sambwise'.

I don't think "verify -v" will fix this, nor is comparing against
the checksum reported by fstat useful, since the comparison is happening against
a revision that doesn't exist yet (i.e. the one being written during the
submit).  The differing server checksums each time are very
interesting -- if it was some sort of translation error it'd at least be
consistent!

There aren't $DateTime$ keywords at play here, are
there?  What's the filetype?  (It *shouldn't*
matter, but...)

Is anyone else submitting files that are this size or larger?  That
seems like the most likely factor to be significant -- if it's specific to
files above a certain threshold I might be inclined to suspect the server
filesystem (e.g. you're writing these files to a RAID that mangles any file
that's larger than some multiple of its stripe size).

If other users are regularly editing and submitting files that size then the
network is one possibility, but it's a little weird that it'd deliver a
scrambled file to the server without perturbing anything else and throwing some
more low-level error.  Do you have anything running on your system
that might be messing with reads of the files under some circumstances (an
overly aggressive virus scanner, a file syncing/backup service that uses a
kernel extension, etc)?



--
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