lblk-write-read-pi - Man Page
Writes and then read with protection information
Synopsis
lblk write-read-pi <uri> [<args>]
Description
Writes and then read with protection information
Required
- <uri>
- Device URI e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 
- --slba 0xNUM
- Start Logical Block Address 
- --nlb NUM
- Number of LBAs (NOTE: zero-based value) 
Optional
- [ --nsid 0xNUM ]
- Namespace Identifier for Command Construction 
- [ --pract NUM ]
- Protection Information Action 
- [ --prchk 0xNUM ]
- Protection Information Check 
- [ --apptag 0xNUM ]
- Application Tag 
- [ --apptag_mask 0xNUM ]
- Application Tag Mask 
- [ --data-input FILE ]
- Path to data input-file 
- [ --meta-input FILE ]
- Path to meta input-file 
- [ --subnqn STRING ]
- Subsystem NQN of the NVMe over Fabrics endpoint e.g. 'nqn.2022-06.io.xnvme:ctrlnode1' 
- [ --hostnqn STRING ]
- The host NQN to use when connecting to NVMe over Fabrics controllers 
- [ --be STRING ]
- xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows' 
- [ --dev-nsid 0xNUM ]
- Namespace Identifier for Device Handle 
- [ --admin STRING ]
- xNVMe admin. command-interface, e.g. 'nvme', 'block' 
- [ --mem STRING ]
- xNVMe buffer/memory manager 
- [ --direct NUM ]
- Bypass layers 
- [ --sync STRING ]
- xNVMe sync. command-interface, e.g. 'nvme', 'block' 
- [ --help ]
- Show usage / help 
See Also
Full documentation at: <https://xnvme.io/>
Author
Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung