NVME-VERIFY(1) | NVMe Manual | NVME-VERIFY(1) |
nvme-verify - Send an NVMe Verify command, return results
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 | -C] [--output-format=<fmt> | -o <fmt>] [--verbose | -v]
The Verify command verifies the integrity of the stored information by reading data and metadata.
-n <nsid>, --namespace-id=<nsid>
-s <slba>, --start-block=<slba>
-c <nlb>, --block-count=<nlb>
-l, --limited-retry
-f, --force-unit-access
-p <prinfo>, --prinfo=<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 |
-r <reftag>, --ref-tag=<reftag>
-m <appmask>, --app-tag-mask=<appmask>
-a <apptag>, --app-tag=<apptag>
-S <storage-tag>, --storage-tag=<storage-tag>
-C, --storage-tag-check
-o <fmt>, --output-format=<fmt>
-v, --verbose
No examples yet.
Part of the nvme-user suite
08/14/2024 | NVMe |