NVME-ZNS-ZONE-MGM(1)

🌈 NVME-ZNS-ZONE-MGM(1) — the NVMe Manual page for nvme-zns-zone-mgmt-send 🌈

🌸 NAME 🌸

nvme-zns-zone-mgmt-send — Zone Management Send command. That’s the whole name vibe, bestie. 💖

🦋 SYNOPSIS 🦋

nvme [<global-options>] zns zone-mgmt-send <device>
                        [--namespace-id=<NUM> | -n <NUM>]
                        [--start-lba=<IONUM>, -s <IONUM>]
                        [--zsaso, -O]
                        [--select-all, -a]
                        [--zsa=<NUM>, -z <NUM>]
                        [--data-len=<IONUM>, -l <IONUM>]
                        [--data=<FILE>, -d <FILE>]

✨ DESCRIPTION ✨

Okay so for the NVMe device you hand over, this issues the Zone Management Send command with the send action you requested. If the send needs extra data, you may specify the data length. If data is required, the input will default to stdin — yes bestie, the terminal is ready to receive. Alternatively, the data may come from a file that can be specified. Slay. 💅

💅 OPTIONS 💅

Heads up: yes, -l / --data-len is listed twice below — that’s literally how the page is serving it, no cap. 🙈

• -n <NUM>, --namespace-id=<NUM> — This is the namespace id you’re targeting. Leave it out and the namespace id of the block device gets used instead. But if you’re issuing the command to a non-block device, this parameter is required — no skipping. The broadcast value 0xffffffff can also be given as all or -1. 👑
• -s <lba>, --start-lba=<lba> — Where the zone you’re managing starts: the starting LBA of the zone to manage send. 🌸
• -l <NUM>, --data-len=<NUM> — Send data buffer length. 📏
• -O, --zsaso — Zone Send Action Specific Option. That’s the whole vibe. ⭐
• -a, --select-all — Sends the command to all zones. Group-chat blast. 📣
• -z <NUM>, --zsa=<NUM> — Zone send action. Pick your move, bestie. 💜
• -l <IONUM>, --data-len=<IONUM> — Buffer length if data required. 🍓
• -d <FILE>, --data=<FILE> — Optional file for data (default stdin). 🫶

👑 GLOBAL OPTIONS 👑

The following options are defined at the top-level nvme command and are available to this subcommand:

• --dry-run — Shows you the command that would be executed, but does not actually execute it. Preview mode, no cap. 💀
• --no-ioctl-probing — Disables probing for 64-bit IOCTL support. 🚫
• --no-retries — Disables retry logic on transient errors. One shot. 🎯
• -o <fmt>, --output-format=<fmt> — Sets the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time — pick your lane. ✨
• --output-format-version=<version> — Picks the output format version. Version 1 keeps the original field naming, while version 2 (default) gives you more consistent and script-friendly field names. Other versions are rejected. 🦋
• --quiet — Suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. 🤫
• --set-options=<key=value>[,<key=value>...] — Sets libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. 🧚
• --timeout=<ms> — Sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). ⏳
• -v, --verbose — Increases the level of detail in the output. May be specified multiple times to further increase verbosity. 🔥

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. 💖

🎀 EXAMPLES 🎀

• Fire off a zone management command with action set to 1 (close zone) at namespace 1’s first zone:

# nvme zns zone-mgmt-send /dev/nvme0 -n 1 -s 0 -z 1

• Drop "hello world" into the zone descriptor for namespace 1’s first zone — this one requires device supports a large enough zone extended data:

# echo "hello world" | nvme zns zone-mgmt-send /dev/nvme0 -n 1 -s 0 -z 0x10

⭐ NVME ⭐

Part of nvme-cli. 👑

---

🫶 That’s the page, bestie! Cute sign-off: NVMe source/version, 10/30/2026 date, and footer flex NVME-ZNS-ZONE-MGM(1). Periodt. 💅