LBLK-IDFY(1)

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

💖 LBLK-IDFY(1) 💖

okay bestie, welcome to lblk-idfy — it's the lblk idfy subcommand from the xNVMe crew, and it's in manual section 1, which is where all the cool user commands live. what does it do? it goes and identifies the namespace for whatever URI you hand it. that's it. that's the whole job. and it eats. 💅

✨ NAME ✨

lblk-idfy — Identify the namespace for the given URI 🦋

✨ SYNOPSIS ✨

lblk idfy <uri> [<args>]

that's the shape of it, bestie. one URI, and then whatever optional args your heart desires. 🌸

✨ DESCRIPTION ✨

so like, the entire vibe of this command is: you point it at a device, and it identifies the namespace for that URI. that's the description, fr fr. no cap, it's that straightforward. 😭✨

✨ REQUIRED ✨

  • <uri> — the device URI, and yeah you gotta give it one, it's required, periodt. for example: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 👑

✨ OPTIONAL ✨

all of these are optional bestie, so pick and choose like you're building a lil outfit 🎀

  • --nsid 0xNUM — the Namespace Identifier used for Command Construction. yes it's a hex number, look at you go 💜
  • --data-output FILE — path to your data output-file, so the output has somewhere cute to live 🍓
  • --subnqn STRING — the Subsystem NQN of the NVMe over Fabrics endpoint. example vibes: 'nqn.2022-06.io.xnvme:ctrlnode1' 🌈
  • --hostnqn STRING — the host NQN you wanna use when connecting to NVMe over Fabrics controllers 🦋
  • --be STRING — the xNVMe backend, like 'linux', 'spdk', 'fbsd', 'macos', 'posix', or 'windows'. pick your fighter ✨
  • --dev-nsid 0xNUM — the Namespace Identifier for the Device Handle. another hex moment, we love to see it 💅
  • --admin STRING — the xNVMe admin. command-interface, e.g. 'nvme' or 'block' 👑
  • --mem STRING — the xNVMe buffer/memory manager 🧚
  • --direct NUM — Bypass layers. it's giving "go straight to the hardware, no middlemen" energy 🔥
  • --help — Show usage / help. when in doubt, ask for help, that's not a flop that's growth 🫶

✨ SEE ALSO ✨

the full documentation is literally right here, bestie: <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, no crumbs left. every flag, every example, every path — all accounted for 💯

okay bye ily, this was xNVMe, dated 09 September 2024, and it's the LBLK-IDFY(1) page. slay, stan, identify those namespaces responsibly 💅✨🦋

📦 where this page comes from