NVME-SNDK-VS-TELE(1)

💖 NAME 💖

Bestie, you're looking at NVME-SNDK-VS-TELE(1), the manual page for nvme-sndk-vs-telemetry-controller-option. Its whole main-character job? Disable/Enable the controller initiated option of the telemetry log page. That's it, that's the vibe. 🎀

✨ SYNOPSIS ✨

nvme [<global-options>] sndk vs-telemetry-controller-option <device>
                               [--disable, -d] [--enable, -e] [--status, -s]

🦋 DESCRIPTION 🦋

Okay so for the NVMe device you pass in, this sends the sndk Vendor Specific set feature command to disable, enable, or get the current status of the controller initiated option of the telemetry log page. Iconic little errand. 💅

The <device> parameter is mandatory — it's the NVMe character device, ex: /dev/nvme0. Don't skip it, she's required. 🫶

🚨 Real talk: this only works on Sandisk devices that support this feature. Results for any other device are undefined. That's not a drill, bestie — undefined behavior is giving chaos, so don't test it on random hardware.

🌸 OPTIONS 🌸

• -d, --disable — Disables the controller initiated option of the telemetry log page. Off she goes. 🙈
• -e, --enable — Enables the controller initiated option of the telemetry log page. Turn it all the way up. 🔥
• -s, --status — Returns the current status — enabled or disabled — of the controller initiated option of the telemetry log page. Vibe check for the setting. 👑

💜 GLOBAL OPTIONS 💜

These are defined at the top-level nvme command and are available to this subcommand. So yes, they're invited to the group chat. 🫶

• --dry-run — Print the command that would be executed, but don't actually execute it. It's giving rehearsal, not the real performance. 🎭
• --no-ioctl-probing — Disable probing for 64-bit IOCTL support.
• --no-retries — Disable retry logic on transient errors.
• -o <fmt>, --output-format=<fmt> — Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time. Pick a lane, bestie. ✨
• --output-format-version=<version> — Select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. Other versions are rejected. No random versions allowed, periodt. 💀
• --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. Shhh, but not suspiciously quiet. 🤫
• --set-options=<key=value>[,<key=value>...] — Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. Very customizable, very demure. 🎀
• --timeout=<ms> — Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). Patience is a virtue, allegedly. ⏳
• -v, --verbose — Increase the level of detail in the output. May be specified multiple times to further increase verbosity. Spill more tea, please. ☕

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. File says one thing, CLI says another? CLI wins, no debate. 👑

🔥 EXAMPLES 🔥

• Disables the controller initiated option of the telemetry log page:

# nvme sndk vs-telemetry-controller-option /dev/nvme0 --disable
# nvme sndk vs-telemetry-controller-option /dev/nvme0 -d

• Enables the controller initiated option of the telemetry log page:

# nvme sndk vs-telemetry-controller-option /dev/nvme0 --enable
# nvme sndk vs-telemetry-controller-option /dev/nvme0 -e

• Gets the current status (enabled or disabled) of the controller initiated option of the telemetry log page:

# nvme sndk vs-telemetry-controller-option /dev/nvme0 --status
# nvme sndk vs-telemetry-controller-option /dev/nvme0 -s

🌈 NVME 🌈

Part of the nvme-user suite. Family business, iykyk. 💖

---

xoxo, NVME-SNDK-VS-TELE(1) 💖 — source/version: NVMe; date: 10/30/2026. Byeee, go slay those telemetry settings! 🦋