NVME-WDC-GET-LATE(1)

📦
version 3.2 · 14 versions
, in arch rolling

💅 NVME-WDC-GET-LATENCY-MONITOR-LOG 💅

okay bestie, so this one lives in the NVMe manual — it's nvme-wdc-get-latency-monitor-log, and it's here to Display latency monitor log page data in human readable format. yes, the whole vibe is "make the numbers make sense" ✨

🌸 SYNOPSIS 🌸

nvme [<global-options>] wdc get-latency-monitor-log <device>

that's it. that's the whole incantation. 🪄

🦋 DESCRIPTION 🦋

So for the NVMe device you hand it, it prints out latency monitor log page data. that's the job. she's straightforward. 💅

The <device> parameter is mandatory and it's gotta be an NVMe character device (ex: /dev/nvme0). no device, no log. sorry bestie, them's the rules 🎀

✨ real talk though: this will only work on WDC devices</> that actually support this log page. Results for any other device are undefined — like, we're not saying your random drive will explode, but we're also not saying it won't. don't come for me. 😭

On success it returns 0, and an error code otherwise. slay 💖

🎀 OPTIONS 🎀

✨ GLOBAL OPTIONS ✨

these are defined up at the top-level nvme command, but they're available to this subcommand too — like the cool older siblings that still let you sit with them 🫶

  • --dry-run — prints the command it would execute, but doesn't actually execute it. it's giving "manifesting without committing". 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. sometimes you just know, y'know? 💀
  • --no-retries — turns off 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, okurrr? 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 and script-friendly field names. any other version gets rejected, no cap. 🚫
  • --quiet — suppresses informational messages. errors are still reported, and --quiet also cancels any --verbose for the library log level. she's quiet but she's still watching. 🤫
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this one invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, comma-separate, go off. 🍓
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). patience is a virtue fr fr ⏳
  • -v, --verbose — increases how much detail you get. you can stack it multiple times to get even more verbose. lore drop after lore drop. 📚
💡 btw these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file, so the CLI stays main character. 👑

🌈 EXAMPLES 🌈

  • Displays the get latency monitor log for the device:
# nvme wdc get-latency-monitor-log /dev/nvme0

look at her go. iconic. 🧚

⭐ NVME ⭐

Part of the nvme-user suite. one big happy family 💜

and that's the page, bestie!! 🎀 written up in the NVMe manual, straight from the nvme-user suite, dated 10/30/2026 — go forth and monitor those latencies, you absolute legend 🦋✨💖

📦 where this page comes from