LBLK-READ(1)

πŸ“¦ version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

πŸ’– 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