Perforce 2006.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 [ -m maxRevs -q -u -v ] file[revRange]...

Description

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

If invoked without arguments, p4 verify computes and displays the MD5 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! If the digests differ, the output line for the corrupt file ends with BAD!

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 filesize and MD5 digest of each file in the Perforce database if and only if no filesize and/or 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. (The -v flag is used only to update the saved digests of archive files which have been deliberately altered outside of Perforce control by a Perforce system administrator.)

-m maxRevs

Limit p4 verify to maxRevs revisions.

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

For details, see the Perforce System Administrator's Guide.

Administrators of very large sites (such as those with tens of millions of revisions) may encounter memory constraints immediately following an upgrade to 2005.1 if they attempt to update file length metadata for the entire repository at once. If this is the case, use the -m maxRevs flag to limit the number of revisions updated per command; p4 verify -u -m 1000000 //... limits file length metadata recomputation to a million files at a time, enabling an administrator to divide file length metadata recomputation over several calls to p4 verify.


Perforce 2006.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-2006 Perforce Software. All rights reserved.
Last updated: 06/23/06