Verify that the server archives are intact
p4 verify reports for each revision of the named files the revision specific information and an MD5 digest (fingerprint) of the revision's contents.
By default, 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. Later uses of p4 verify will compare the newly computed version to the saved version; if they differ, the output line will end with BAD! Once stored, a digest is not re-stored unless the -v flag is used. This can be used to update the saved digest if the archive was changed deliberately.
| -q | Run quietly; only display the output if there are errors. |
| -u | Store the digest in the Perforce database. Future uses of p4 verify will compare the computed version against this stored version. |
| -v | Store the digest in the Perforce database, even if there's already an entry for that file. |
| g_opts | See global options section. |
|
Can File Arg Use Revision Specifier? |
Can File Arg Use Revision Range? |
Minimal Access Level Required |
|---|---|---|
| Yes | Yes | super |