NVME-WRITE(1) | NVMe Manual | NVME-WRITE(1) |
nvme-write - Send an NVMe write command, provide results
nvme-write <device> [--start-block=<slba> | -s <slba>]
[--block-count=<nlb> | -c <nlb>]
[--data-size=<size> | -z <size>]
[--metadata-size=<size> | -y <size>]
[--ref-tag=<reftag> | -r <reftag>]
[--data=<data-file> | -d <data-file>]
[--metadata=<metadata-file> | -M <metadata-file>]
[--prinfo=<prinfo> | -p <prinfo>]
[--app-tag-mask=<appmask> | -m <appmask>]
[--app-tag=<apptag> | -a <apptag>]
[--limited-retry | -l]
[--force-unit-access | -f]
[--dir-type=<type> | -T <type>]
[--dir-spec=<spec> | -S <spec>]
[--dsm=<dsm> | -D <dsm>]
[--show-command | -v]
[--dry-run | -w]
[--latency | -t]
The Write command writes the logical blocks specified by the command to the medium from the data data buffer provided. Will use stdin by default if you don’t provide a file.
--start-block=<slba>, -s <slba>
--block-count, -c
--data-size=<size>, -z <size>
--metadata-size=<size>, -y <size>
--data=<data-file>, -d <data-file>
--metadata=<metadata-file>, -M <metadata-file>
--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>
--limited-retry, -l
--force-unit-access, -f
-T <type>, --dir-type=<type>
-S <spec>, --dir-spec=<spec>
-D <dsm>, --dsm=<dsm>
-v, --show-cmd
-w, --dry-run
-t, --latency
No examples yet.
Part of the nvme-user suite
04/24/2020 | NVMe |