Perforce 2002.1 Command Reference
<< Previous Chapter
p4 users
Table of Contents
Index
Perforce on the Web
Next Chapter >>
p4 where

p4 verify


Synopsis

Verify that the server archives are intact.

Syntax

p4 [g-opts] verify [ -q -u -v ] file[revRange]...

Description

p4 verify reports for each revision of the named files the revision specific information and an MD5 digest (fingerprint) of the revision's contents.

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

super

It is good administrative practice to run p4 verify -qu //... (to generate new checksums and verify old ones across your entire depot) as part of your nightly backup process, as well as immediately before any server upgrade.

Similarly, it is also good administrative practice to use p4 verify -q //... (to verify the integrity of your files) after restoring from backups, or immediately following any server upgrade.

If p4 verify returns errors, contact Perforce technical support.

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


Perforce 2002.1 Command Reference
<< Previous Chapter
p4 users
Table of Contents
Index
Perforce on the Web
Next Chapter >>
p4 where
Please send comments and questions about this manual to [email protected].
Copyright 1999-2002 Perforce Software. All rights reserved.
Last updated: 04/03/02