XNVME-FEATURE-SET(1)

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

💖 xnvme-feature-set — the manual, but make it make sense 💖

okay bestie, so this is a page from the xNVMe manual set, and it's literally all about xnvme-feature-set. yes it's a manpage, no it doesn't have to be boring. sit with me, grab a boba, let's go 🧋✨

🌸 NAME 🌸

xnvme-feature-set — Execute a Set-Features Command

like. that's the whole thing. it sets features. it's giving "does exactly what it says on the tin" 💅

✨ SYNOPSIS ✨

xnvme feature-set <uri> [<args>]

that's the shape of it, babe. a <uri>, then whatever args you feel like bringing along 🎀

🦋 DESCRIPTION 🦋

Execute a Set-Features Command.

periodt. that's the vibe. no notes. 🔥

👑 REQUIRED 👑

these ones? not optional. you need them. no skips, no shortcuts, main character requirements only:

  • <uri> — Device URI, e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1'. it's how you tell xNVMe which device you're talking to, so like… pick the right one 🙈
  • --fid 0xNUM — Feature Identifier. the ID of the feature you're setting. gotta name it to claim it, iykyk 💖
  • --feat 0xNUM — Feature, e.g. cdw12 content. this is the actual feature content you're handing over. slay ✨

🎀 OPTIONAL 🎀

now the fun part — the little extras. all of these are square-bracketed in the synopsis because they're optional, so you can absolutely just not 💅

  • [ --nsid 0xNUM ] — Namespace Identifier for Command Construction. tells the command how to build itself, namespace-wise 🌸
  • [ --save ] — Save. yes bestie, save it 🫶
  • [ --cdw12 0xNUM ] — Command Dword12. a whole dword, twelve'd 🔥
  • [ --data-input FILE ] — Path to data input-file. your file, your data, your moment 💜
  • [ --data-nbytes NUM ] — Data size in bytes. how many bytes, precisely. numbers don't lie ngl 🦋
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. it's the fabrics girly era 🌈
  • [ --hostnqn STRING ] — The host NQN to use when connecting to NVMe over Fabrics controllers. this is your nqn in the fabrics situation 💫
  • [ --be STRING ] — xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter ✨
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle. the nsid for the handle itself, not the command. different thing, stay with me 😭
  • [ --admin STRING ] — xNVMe admin. command-interface, e.g. 'nvme', 'block'. which admin interface you're rolling with 👑
  • [ --mem STRING ] — xNVMe buffer/memory manager. who's handling the memory, bestie 🧚
  • [ --direct NUM ] — Bypass layers. layers? bypassed. we're going straight through 💀
  • [ --help ] — Show usage / help. when in doubt, ask for help. literally always valid 🌸

🌈 SEE ALSO 🌈

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

go read it. it's free. it's iconic. it's the whole lore drop 📚✨

💜 AUTHOR 💜

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. absolute legend behavior, no cap 🙌

🫶 quick vibe check before you go: every flag above is exactly as it appears in the original page — same names, same placeholder syntax, same example values. I just gave them a personality. the facts did not move. 💖

and that's the whole page, bestie!! this one came out of the xNVMe manual, version date 09 September 2024, page XNVME-FEATURE-SET(1) — so if you cite it in your group chat, that's your receipt 🎀✨💅

📦 where this page comes from