XNVME-IDFY-CTRLR(1)

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

💖 xnvme-idfy-ctrlr — the xvme manual page, bestie edition 💖

okay so real quick, this page lives in the xNVMe manual, section 1 (that's the "run it in your shell" section, iykyk). and it's about ✨identifying controllers✨. let's get into it.

🌸 NAME 🌸

xnvme-idfy-ctrlr — Identify the given Controller

like. that's it. that's the whole job. she identifies the given controller and she does it flawlessly.

🦋 SYNOPSIS 🦋

xnvme idfy-ctrlr <uri> [<args>]

✨ DESCRIPTION ✨

Identify the given Controller 🎀

no like, genuinely, that is the entire description. iconic of her honestly. she said "my purpose is stated and I'm not elaborating." main character energy fr fr.

👑 REQUIRED 👑

  • <uri> — the Device URI, bestie. this is mandatory, you cannot skip it, she will simply not run. examples of what she'll accept:
/dev/nvme0n1
0000:01:00.1
10.9.8.1.8888
\.PhysicalDrive1

see that last one? yes, that backslash is really there. copy it exactly. 💅

🧚 OPTIONAL 🧚

these are the lil extras you can sprinkle on top. all optional, all slay.

  • [ --data-output FILE ] — Path to data output-file. like, where do you want the data to go? tell her. she'll put it there. 💖
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. yes the whole NQN string. it's giving very specific.
  • [ --hostnqn STRING ] — The host NQN to use when connecting to NVMe over Fabrics controllers. your host's little name tag for the fabrics party 🎀
  • [ --be STRING ] — xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter. 💀
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle. note the 0x — she wants that hex, bestie, don't come at her with a plain decimal and expect it to hit.
  • [ --admin STRING ] — xNVMe admin. command-interface, e.g. 'nvme', 'block'. which admin interface are we vibing with today 🦋
  • [ --mem STRING ] — xNVMe buffer/memory manager. who's holding the buffers. someone has to.
  • [ --direct NUM ] — Bypass layers. yes. skip the middlemen. go straight there. direct. periodt.
  • [ --help ] — Show usage / help. when in doubt, ask her for help. she's nice about it, promise 🫶

🌈 SEE ALSO 🌈

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

that's the whole link. go there. it's got the whole lore, the full documentation, everything. no cap. 🔥

💜 AUTHOR 💜

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

okay a legend, honestly. respect. 🙇‍♀️

bestie PSA: every flag above is doing real work, so if a command isn't behaving, check you spelled the URI right before you blame her. 💀

and that's the page!! this one came out with xNVMe as the source/version and the date 09 September 2024, so if you're citing her, that's the tea. mwah, go identify some controllers, you got this 👑💅✨

📦 where this page comes from