NVME-OCP-LATENCY-(1)

💅 nvme-ocp-latency-monitor-log — the OCP latency monitor log page, but make it readable

okay so bestie, this is a page from the NVMe Manual (section 1, NVME-OCP-LATENCY-(1) if you're keeping score) and honestly? it's giving "niche but iconic." we're pulling the latency monitor log page off your drive and showing it in a human readable format instead of a wall of hex. you're welcome. 🎀

---

✨ NAME ✨

nvme-ocp-latency-monitor-log — display latency monitor log page data in human readable format 🌸

---

🦋 SYNOPSIS 🦋

nvme [<global-options>] ocp latency-monitor-log <device> [--no-uuid | -n]

---

💖 DESCRIPTION 💖

so for the NVMe device you hand over, you get the latency monitor log page data. that's the whole vibe. ✨

the <device> parameter is mandatory, no skipping it, no "i'll do it later" — and it can be either:

• the NVMe character device, like ex: /dev/nvme0
• or the block device, like ex: /dev/nvme0n1

either one works, pick your fighter 🫶

⚠️ major caveat, no cap: this will only work on OCP compliant devices supporting this log page. results for any other device are undefined. literally undefined. we don't know what happens. don't be the main character who finds out the hard way 💀

on success it returns 0, error code otherwise. that's it, that's the contract. 👑

---

🌈 OPTIONS 🌈

• -n, --no-uuid — do not try to automatically detect the UUID index for this command (default UUID index to 0). lowkey useful when the auto-detect is being extra 🙈

---

⭐ GLOBAL OPTIONS ⭐

these bad boys are defined at the top-level nvme command, and they're available to this subcommand too. group-chat inheritance, iykyk 💅

• --dry-run — print the command that would be executed, but do not actually execute it. all the tea, none of the commitment ✨
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. one shot, one opportunity 🎯
• -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. so don't try it 🙅‍♀️
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "i'm not reading all that" 💀
• --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.
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patient queen behavior 👑
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. say it again, louder 📢

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. the flag wins, periodt. 🏆

---

🧚 EXAMPLES 🧚

• displays the get latency monitor log for the device:

# nvme ocp latency-monitor-log /dev/nvme0

that's it. that's the post. 🌟

---

👑 NVME 👑

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

---

okay that's the whole page!! and for the cute sign-off: this lil masterpiece lives under the NVMe source, dated 10/30/2026, and it's filed as NVME-OCP-LATENCY-(1) in the manual. go forth and monitor those latencies, bestie 🌈💖✨