NVME-TELEMETRY-LOG(1)

📦
version 3.2 · 14 versions
, in arch rolling

💅 NVME-TELEMETRY-LOG — the nvme manual, bestie edition ✨

okay so real talk, this is the NVME-TELEMETRY-LOG(1) page from the NVMe Manual, and it's basically the nostalgic little corner of nvme-cli. grab a strawberry 🍓 and let's get into it.

🌸 NAME 🌸

nvme-telemetry-log — pulls the Telemetry Host-Initiated log page off an NVMe device. yes, queen. but also: it's deprecated 🙈 (more on that in a sec).

🎀 SYNOPSIS 🎀

nvme [<global-options>] telemetry-log <device>
                        [--output-file=<file> | -O <file>]
                        [--host-generate=<gen> | -g <gen>]

like, you give it a device, you can point it at an output file with --output-file=<file> or -O <file>, and you can pass a generation with --host-generate=<gen> or -g <gen>. cute, simple, iconic. 💖

🦋 DESCRIPTION 🦋

so here's the tea: this is a deprecated alias for nvme-log-telemetry(1). it's still hanging around for all the scripts written against nvme-cli versions older than 3.0. the options and behavior are identical — literally the only thing kept is the top-level command name. no cap. 🫶

if you're writing new scripts, please bestie, use nvme log telemetry instead. this alias prints a deprecation warning on stderr and may be removed in a future release — so don't get too attached, she's on her way out. 😭

for the full option reference, go read nvme-log-telemetry(1). she has the whole menu.

✨ GLOBAL OPTIONS ✨

these are defined at the top-level nvme command and they're available to this subcommand too. so you get the whole squad: 👑

  • --dry-run — prints the command that would be executed but doesn't actually run it. it's giving "manifesting but not doing" energy 💭
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support. no poking around. 🙅
  • --no-retries — disables retry logic on transient errors. one shot, one opportunity. 💀
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. only one output format at a time, okay? don't be greedy. 🎀
  • --output-format-version=<version> — picks the output format version. version 1 uses the original field naming, while version 2 (the default) gives you more consistent, script-friendly field names. any other version gets rejected — not on the menu. 🚫
  • --quiet — suppresses informational messages. errors still get reported, and heads up: --quiet cancels any --verbose for the library log level. they literally cannot coexist, it's a vibe check. 🔇
  • --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. very demure, very configurable. ⭐
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit (0xffffffff). she'll wait forever, lowkey romantic. ⏳
  • -v, --verbose — increases the level of detail in the output. can be specified multiple times to crank the verbosity even higher. go off, stack it. 🔥
also — these options can be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. always. rules are rules. 💅

🌈 EXAMPLES 🌈

No Examples

that's it. that's the section. the well is dry, bestie. 🏜️

👑 NVME 👑

part of the nvme-user suite. one of us, one of us. 🌸

💜 SEE ALSO 💜

and that's the whole page, bestie! 🧚

little sign-off: this lovely thing is from the NVMe source, dated 10/30/2026. screenshot it, frame it, whatever — it's iconic. 🎀💖🌀

k bye, go run nvme log telemetry instead, i'm begging 🫶💅

📦 where this page comes from