Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 CLI Documentation | 2025.2

# p4 graph verify (graph)

Verify repo integrity.

## Syntax

    p4 graph verify [-q] -n //repo/name

Syntax and naming conventions

## Description

Traverse the directed acyclic graph (DAG) of the repo to verify that each blob object exists as expected in the archive.

LFS (Large File Storage) archives are also verified.

In the output, a line appears for each file in the repo because the command generates a SHA1 on each repo blob in real time. With a command such as

`p4 graph verify -n //gd1/repo1`

each line might appear in a manner similar to the following:

`e69de29bb2d1d6434b8b29ae775ad8c2 gd1/repo1.git/objects/e6/9de29bb2d1d6434b8b29ae775ad8c2`

## Options

Option | Description
--- | ---
`-n` | (required) The name of repo to verify.
`-q` | (optional) Suppress output in the case of successful verification of the blob. However, in the case of a failure, display a message indicating the problem, such as: the specified repo does not exist the repo does not contain each of the expected blob objects, such that, for that blob, SHA1 computed in real time does not match the expected SHA1 no SHA1 can be computed because the blob is missing If used, `-q` must precede `-n`

## Usage notes

Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required
--- | --- | ---
N/A | N/A | `list`

## Related commands

To recompute object refcounts in the object table. | p4 graph recompute-refcnts (graph)
To delete refhist records for a repo. | p4 graph purge-refhist (graph)

Your search for returned results