ZONED-MGMT(1)

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

💅 ZONED-MGMT(1) — bestie's guide to zoned-mgmt

okay so listen. this is the zoned-mgmt page from the xNVMe manual, section 1. it's a whole lil tool and we're gonna go through it together, every flag, every number, no skips. grab a snack 🍓

✨ NAME ✨

zoned-mgmt — Zone Management Send Command with custom action 💫

like, that's the whole vibe. you're sending a zone management command, but you get to pick the action. main character energy fr.

✨ SYNOPSIS ✨

zoned mgmt <uri> [<args>]

that's it. that's the whole shape of it. a URI, then whatever args your heart desires 🫶

✨ DESCRIPTION ✨

Zone Management Send Command with custom action.

short, sweet, iconic. you point it at a device, you tell it what zone action to do, it does the thing. periodt. 💅

✨ REQUIRED ✨

these are the non-negotiables, bestie. no skipping. 😤

  • <uri> — the Device URI. like where your device lives. examples they gave us: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1'. yes the last one has a backslash in front, that's on purpose, keep it exactly like that 🙈
  • --slba 0xNUM — Start Logical Block Address. where the party starts in block-land. it's in hex, 0xNUM style ✨
  • --zsa 0xNUM — Zone Send Action. this is the whole point of the tool, the action you're sending. the options are:
    • Close=0x1
    • Finish=0x2
    • Open=0x3
    • Reset=0x4
    • Offline=0x5
    • Zone Descriptor Extension=0x10

yes that last one is 0x10 and not 0x6, do NOT come for me, that's literally what the page says. iykyk 😌

✨ OPTIONAL ✨

these are the little extras. the accessories to your outfit. all of them are wrapped in [ ] so you know they're optional, but honestly some of them are lowkey essential depending on your setup 💖

  • [ --nsid 0xNUM ] — Namespace Identifier, used for Command Construction. 0xNUM so hex again, bestie 🔥
  • [ --all ] — Select / Affect all. it does what it says, all of it, the whole thing 🌈
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint. the example given is 'nqn.2022-06.io.xnvme:ctrlnode1' — yeah that's a whole mouthful, copy-paste is your friend 🎀
  • [ --hostnqn STRING ] — The host NQN to use when connecting to NVMe over Fabrics controllers. this is your NQN in the fabrics relationship 💜
  • [ --be STRING ] — the xNVMe backend. pick your fighter: 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows' ⭐
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle. yes this is different from --nsid up above, one's for the command construction and one's for the device handle, they are NOT the same thing, keep them straight bestie 😭
  • [ --admin STRING ] — xNVMe admin command-interface. options are 'nvme' or 'block' 👑
  • [ --mem STRING ] — xNVMe buffer/memory manager. your memory, your manager, your choice 🧚
  • [ --direct NUM ] — Bypass layers. sneaky sneaky, going around stuff 🦋
  • [ --sync STRING ] — xNVMe sync command-interface. again with the 'nvme' or 'block' energy ✨
  • [ --help ] — Show usage / help. the classic. the beloved. when in doubt, ask for help 💖

✨ SEE ALSO ✨

✨ AUTHOR ✨

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. shoutout to them, absolute legends for writing all this down for us 🫶

okay that's the whole page, you made it, i'm so proud of you 💅✨

this was the xNVMe manual, and it's dated 09 September 2024 — so if you're reading this way later, just know the vibes are still immaculate. go send some zone management commands, bestie, you got this 🌸👑💖

📦 where this page comes from