LBLK-READ(1)
π LBLK-READ(1) β the xNVMe glow-up π
okay bestie, gather round, because today we're reading data (and optionally metadata, we love an optional queen) and honestly? it's giving main character. this is lblk-read, part of the xNVMe family, and she's here to pull bytes off your device and put them wherever you tell her to. no cap.
β¨ SYNOPSIS β¨
lblk read <uri> [<args>]
that's it. that's the whole vibe. <uri> is mandatory, the args are your little garnish. π
πΈ DESCRIPTION πΈ
Read data and optionally metadata. literally what it says on the tin, and she does it flawlessly. π
π REQUIRED π (yes you actually have to give her these, she's not asking twice)
<uri>β Device URI, bestie. like, the address of the thing you wanna read from. examples so you get the vibe:'/dev/nvme0n1','0000:01:00.1','10.9.8.1.8888','\.PhysicalDrive1'. pick your fave, she supports them all π«Ά--slba 0xNUMβ Start Logical Block Address. where the reading begins, the origin story, the opening scene. β¨--nlb NUMβ Number of LBAs. NOTE: this is a zero-based value, so don't come for her when your math is off, the manual literally told you. π
π¦ OPTIONAL π¦ (the fun extras, the accessories to the outfit)
[ --nsid 0xNUM ]β Namespace Identifier for Command Construction. giving the command a lil address label. π·οΈ[ --data-output FILE ]β Path to data output-file. where the actual data lands. your data's new home. π‘[ --meta-output FILE ]β Path to meta output-file. same energy but for the metadata, because metadata deserves her own room too. π[ --subnqn STRING ]β Subsystem NQN of the NVMe over Fabrics endpoint. e.g.'nqn.2022-06.io.xnvme:ctrlnode1'. fabrics girlies rise π[ --hostnqn STRING ]β The host NQN to use when connecting to NVMe over Fabrics controllers. this is your name when you slide into the fabrics controller's DMs. π[ --be STRING ]β xNVMe backend. the options are'linux','spdk','fbsd','macos','posix','windows'. choose your fighter. π[ --dev-nsid 0xNUM ]β Namespace Identifier for Device Handle. different nsid, different purpose, don't mix them up bestie. π[ --admin STRING ]β xNVMe admin. command-interface, e.g.'nvme','block'. the admin is in charge, respect her. π[ --mem STRING ]β xNVMe buffer/memory manager. she handles the memory so you don't have to. iconic. π[ --direct NUM ]β Bypass layers. yes literally, skip the middlemen, go straight to the source. main character doesn't wait in line. β[ --sync STRING ]β xNVMe sync. command-interface, e.g.'nvme','block'. syncing up like a good group chat. π[ --help ]β Show usage / help. the ultimate "girl help" but make it a flag. π
π₯ SEE ALSO π₯
Full documentation at: <https://xnvme.io/> β go, read, be obsessed. π
π AUTHOR π
Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. slay, Simon. π
and that's the tea, bestie β this page came straight out of xNVMe, dated 09 September 2024, and it's LBLK-READ(1) forever and always. periodt. π
β¨
π¦ where this page comes from
- alpine 3.24: xnvme-doc 0.7.5-r1 Β· BSD-3-Clause
- epel 9: xnvme-tools 0.7.5-3.el9 Β· BSD-3-Clause
- fedora 43: xnvme-tools 0.7.5-5.fc43 Β· BSD-3-Clause
- fedora 44: xnvme-tools 0.7.5-6.fc44 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms