XNVME_TESTS_SCC-IDFY(1)

📦 version 0.7.5, in alpine 3.24

💖 NAME 💖

hii bestie 🫶 welcome to the xnvme_tests_scc-idfy(1) page from the xNVMe manual — yes, that’s the manual name, and we’re here to make this whole thing make sense, fr fr.

xnvme_tests_scc-idfy — Print SCC related Controller and Namespace identification ✨

🌸 SYNOPSIS 🌸

okay so the whole vibe is literally this:

xnvme_tests_scc idfy <uri> [<args>]

🦋 DESCRIPTION 🦋

Print SCC related Controller and Namespace identification. That’s the job, bestie — it’s giving “just print the SCC-related controller and namespace ID info” and honestly? slay 💅

🎀 REQUIRED 🎀

  • <uri> — Device URI, e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 👑

✨ OPTIONAL ✨

  • --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

🌈 SEE ALSO 🌈

Full documentation at: https://xnvme.io/ — go be nosy, bestie 🧚

💜 AUTHOR 💜

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

and that’s the whole page, bestie 💖 cute little sign-off: source/version is xNVMe, date is 09 September 2024, and the page tag is XNVME_TESTS_SCC-IDFY(1) — mwah 💋✨

📦 where this page comes from