LBLK-WRITE-DIR(1)

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

πŸ’– lblk-write-dir(1) πŸ’–

okay so bestie, welcome to lblk-write-dir β€” that's the page you're on, section 1 of the manual, and she's from xNVMe 🌸. Buckle up, this one writes directive specific data and, if you want, metadata too. It's giving ✨purpose-built✨.


✨ NAME ✨

lblk-write-dir β€” writes directive specific data and optionally metadata πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

lblk write-dir <uri> [<args>]

πŸ’œ DESCRIPTION πŸ’œ

Writes directive specific data and optionally metadata. That's the whole vibe, no cap. You point it at a device, you tell it where to write, you hand it the goods. Simple. Iconic. πŸŽ€


πŸ‘‘ REQUIRED πŸ‘‘

These ones are non-negotiable, bestie. No skipping.

  • <uri> β€” the Device URI, like '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', or '\.PhysicalDrive1' πŸ™ˆ
  • --slba 0xNUM β€” Start Logical Block Address. Where the party begins. πŸ“
  • --nlb NUM β€” Number of LBAs. ⚠️ NOTE: this is a zero-based value, so heads up, the math is mathing differently than you might expect.

πŸŽ€ OPTIONAL πŸŽ€

All of these are optional, so take what you need and leave the rest, queen. ✨

  • [ --nsid 0xNUM ] β€” Namespace Identifier for Command Construction
  • [ --data-input FILE ] β€” Path to data input-file πŸ“‚
  • [ --meta-input FILE ] β€” Path to meta input-file πŸ“‚
  • [ --dtype 0xNUM ] β€” Directive type; Identify 0x0, Streams 0x1
  • [ --dspec 0xNUM ] β€” Directive specification associated with directive type
  • [ --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 🫢 (she's always there for you)

🌈 SEE ALSO 🌈

Full documentation at: <https://xnvme.io/> β€” go read it, iykyk πŸ“š


πŸ’– AUTHOR πŸ’–

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung 🫑


and that's the whole page, bestie!! this absolute banger of a manpage is brought to you by xNVMe, dated 09 September 2024, and she lives at LBLK-WRITE-DIR(1) forever and ever. go write some directive data. slay. πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from