p4 verify

Synopsis

Syntax

Description

If invoked without arguments, p4 verify computes and displays the digest of each revision. If a revision is missing from the archive and therefore can't be reproduced, the revision's output line ends with MISSING!

To save MD5 fingerprints in the Perforce database, use p4 verify -u. Subsequent invocations of p4 verify compute checksums for the desired files and compare them against those stored by p4 verify -u. If the checksums differ, the output line for the corrupt file ends with BAD!

Once stored, a digest is not recomputed unless p4 verify -v flag is used to overwrite it. The -v flag is generally used only to update the saved digest of archive files which have been deliberately altered outside of Perforce control by a Perforce system administrator.

Options

-q	Run quietly; verify the integrity of files for which MD5 digests have previously been generated, and only display output if there are errors.
-u	Store the MD5 digest of each file in the Perforce database if and only if no digest has been previously stored. Subsequent uses of p4 verify will compare the computed version against this stored version.
-v	Store the MD5 digest of each file in the Perforce database, even if there's already a digest stored for that file, overwriting the existing digest.
g-opts	See the Global Options section.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
Yes	Yes	admin

• If p4 verify returns errors, contact Perforce technical support.

• It is good administrative practice to regularly verify the integrity of your depot files with p4 verify -q //...

Because subsequent verifications can only be performed against previously stored signatures, it is also good practice to regularly generate checksums with p4 verify -u.

For more about good administrative practices, see the Perforce System Administrator's Guide.

• As of Release 2003.2, p4 verify -u is obsolescent, because Perforce Servers at Release 2003.2 and higher automatically generate and store MD5 checksums of files upon file submission. (You must still run p4 verify -u at least once following an upgrade to 2003.2, to generate signatures for any pre-2003.2 files for which signatures were not generated.)