LBLK-WRITE(1)

📦 version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

💖 LBLK-WRITE(1) 💖

okay bestie, so this is the lblk-write page from xNVMe — she's a lil command that writes data and, if you want, some metadata too. no big deal. just data. going places. slay. 💅

✨ NAME ✨

lblk-write — Writes data and optionally metadata 🦋

✨ SYNOPSIS ✨

lblk write <uri> [<args>]

like. that's the whole vibe. <uri> first, then whatever args your heart desires. 🫶

✨ DESCRIPTION ✨

Writes data and optionally metadata.

yep that's it, that's the girl. she writes data. she optionally writes metadata. main character energy, honestly. 👑

✨ REQUIRED ✨

these are not optional bestie, you literally cannot skip them, the command will simply not be okay with it. 😭

  • <uri> — the Device URI, i.e. where your device lives. examples that are valid: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' ✨
  • --slba 0xNUM — Start Logical Block Address. the starting point. where the writing begins. the origin story. 📍
  • --nlb NUM — Number of LBAs. and listen — NOTE: zero-based value. zero-based!! don't come for me when you're off by one, i warned you. 💀

✨ OPTIONAL ✨

these ones are the optional girlypops. sprinkle them in as needed. 🌸

  • [ --nsid 0xNUM ] — Namespace Identifier for Command Construction.
  • [ --data-input FILE ] — Path to data input-file. this is where your data is coming from, bestie. 📂
  • [ --meta-input FILE ] — Path to meta input-file. same energy, but for the meta. 🎀
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint. example: 'nqn.2022-06.io.xnvme:ctrlnode1'. yes it looks like a password, no it's not, it's just NQN things. 🧚
  • [ --hostnqn STRING ] — The host NQN to use when connecting to NVMe over Fabrics controllers. your host's lil name tag at the fabrics party. 💜
  • [ --be STRING ] — xNVMe backend. options include: 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter. ⭐
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle. (yes, different from --nsid. they're siblings. don't mix them up. 🙈)
  • [ --admin STRING ] — xNVMe admin. command-interface, e.g. 'nvme', 'block'. the admin is in charge, obviously. 👑
  • [ --mem STRING ] — xNVMe buffer/memory manager. someone's gotta manage the memory. 🔥
  • [ --direct NUM ] — Bypass layers. going straight to the source, no middlemen, no small talk. 💅
  • [ --sync STRING ] — xNVMe sync. command-interface, e.g. 'nvme', 'block'. it's giving... sync. 🌈
  • [ --help ] — Show usage / help. the classic. the icon. the one you should've run first. 😭

✨ SEE ALSO ✨

Full documentation at: <https://xnvme.io/>

go read it, i'll wait, it's lowkey iconic. 📖✨

✨ AUTHOR ✨

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. king behavior, fr fr. 🫶

okay and finally, the lil sign-off at the bottom of the page — this whole thing is from xNVMe, dated 09 September 2024, and it lives in section LBLK-WRITE(1). that's the tea. periodt. 🍓💖

📦 where this page comes from