NVME-VERIFY(1) | NVMe Manual | NVME-VERIFY(1) |
NAME¶
nvme-verify - Send an NVMe Verify command, return results
SYNOPSIS¶
nvme-verify <device> [--namespace-id=<nsid> | -n <nsid>]
[--start-block=<slba> | -s <slba>]
[--block-count=<nlb> | -c <nlb>]
[--limited-retry | -l]
[--force-unit-access | -f]
[--prinfo=<prinfo> | -p <prinfo>]
[--ref-tag=<reftag> | -r <reftag>]
[--app-tag-mask=<appmask> | -m <appmask>]
[--app-tag=<apptag> | -a <apptag>]
[--storage-tag<storage-tag> | -S <storage-tag>]
[--storage-tag-check<storage-tag-check> | -C <storage-tag-check>]
DESCRIPTION¶
The Verify command verifies the integrity of the stored information by reading data and metadata.
OPTIONS¶
--namespace-id=<nsid>, -n <nsid>
--start-block=<slba>, -s <slba>
--block-count=<nlb>, -c <nlb>
--limited-retry, -l
--force-unit-access, -f
--prinfo=<prinfo>, -p <prinfo>
Bit | Description |
3 | PRACT: Protection Information Action. When set to 1, PI is stripped/inserted on read/write when the block format’s metadata size is 8. When set to 0, metadata is passes. |
2:0 | PRCHK: Protection Information Check: |
2 | Set to 1 enables checking the guard tag |
1 | Set to 1 enables checking the application tag |
0 | Set to 1 enables checking the reference tag |
--ref-tag=<reftag>, -r <reftag>
--app-tag-mask=<appmask>, -m <appmask>
--app-tag=<apptag>, -a <apptag>
--storage-tag=<storage-tag>, -S <storage-tag>
--storage-tag-check=<storage-tag-check>, -C <storage-tag-check>
EXAMPLES¶
No examples yet.
NVME¶
Part of the nvme-user suite
04/15/2023 | NVMe |