XNVME-IDFY(1)

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

✨ XNVME-IDFY ✨

okay bestie, welcome to xnvme-idfy, a page from the xNVMe manual (that's section 1, the "run it in your shell" section 💅). we're doing a User-defined Identify Command today and honestly? iconic behavior.

🌸 NAME 🌸

xnvme-idfy — Execute an User-defined Identify Command 🦋

🎀 SYNOPSIS 🎀

xnvme idfy <uri> [<args>]

💖 DESCRIPTION 💖

Execute an User-defined Identify Command. that's it, that's the whole vibe. you point it at a device, you hand it a controller-or-namespace struct command, and it goes and asks the device stuff. main character energy, no cap. 🔥

👑 REQUIRED 👑

these are not optional, bestie. you literally cannot skip them, the command will simply not eat. 🫶

  • <uri> — Device URI, e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1'. it's giving "where is the device, ma'am". 📍
  • --cns 0xNUM — Controller or Namespace Struct. the 0xNUM is a hex number, yes you have to actually put a number there, we can't do it for you. 💀

✨ OPTIONAL ✨

the little extras, the accessories to the fit. add them if you want, skip them if you don't. 🌈

  • [ --cntid 0xNUM ] — Controller Identifier. tells it which controller, in hex, because we live in a hex world now. 🔢
  • [ --nsid 0xNUM ] — Namespace Identifier for Command Construction. construction!! we're building a command and this namespace id is a structural beam. 🏗️
  • [ --setid 0xNUM ] — NVM Set Identifier. yes it's a different id from the other ids, they're all different, i know, i know. 😭
  • [ --uuid 0xNUM ] — Universally Unique Identifier. it's unique and it's universal and it's a hex number. slay. ⭐
  • [ --data-output FILE ] — Path to data output-file. where the data goes to live. give it a filename, it'll write there. 📁
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. it's a string, not a hex number, don't get it twisted. 🧵
  • [ --hostnqn STRING ] — The host NQN to use when connecting to NVMe over Fabrics controllers. that's your name in the fabric, be proud of it. 🫶
  • [ --be STRING ] — xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter. 🥊
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle. yes, ANOTHER nsid. this one is for the device handle specifically. not the same as the command-construction one. keep up, bestie. 💅
  • [ --admin STRING ] — xNVMe admin. command-interface, e.g. 'nvme', 'block'. choose how you wanna talk to admin. 👑
  • [ --mem STRING ] — xNVMe buffer/memory manager. who's handling the memory today? you decide. 🧠
  • [ --direct NUM ] — Bypass layers. just a plain NUM here, not hex, don't @ me. go straight to the metal, lowkey rebellious. 🚀
  • [ --help ] — Show usage / help. when in doubt, ask for help. no shame in it. 🙈

🦋 SEE ALSO 🦋

Full documentation at: <https://xnvme.io/> — go read it, it's giving knowledgeable. 📚

💜 AUTHOR 💜

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. we love a credited author. 👏

and that's the whole page, bestie!! this was xNVMe manual page, version dated 09 September 2024, and you just read XNVME-IDFY(1). periodt. 💅✨🎀

📦 where this page comes from