NVME-LOG-PREDICTAB(1)

💅 nvme-log-predictable-lat — predictable latency per NVM set log, bestie 💅

okay so you're looking at nvme-log-predictable-lat, and this whole page is from the NVMe Manual, aka NVME-LOG-PREDICTAB(1). It's giving “send the Predictable latency per NVM set log page request, get the result and log back” energy, and honestly? iconic. periodt. 💖

🌸 NAME 🌸

nvme-log-predictable-lat — Send Predictable latency per NVM set log page request, returns result and log. 💅

✨ SYNOPSIS ✨

bestie, the shape of this command is literally:

       nvme [<global-options>] log predictable-lat <device>
                               [--nvmset-id=<nvmset_id> | -i <nvmset_id>]
                               [--raw-binary | -b]

🎀 DESCRIPTION 🎀

This command retrieves the NVMe Predictable latency per NVM set log page from an NVMe device and gives you the returned structure. 🫶

The <device> parameter is mandatory, bestie — not optional, not vibes-only. It may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). 🌈

On success, the returned Predictable latency per NVM set log structure may be returned in one of several ways depending on the option flags: the structure may be parsed by the program and printed in a readable format, or the raw buffer may be printed to stdout for another program to parse. it's giving “choose your own output adventure” ✨

🦋 OPTIONS 🦋

• -i <nvmset_id>, --nvmset-id=<nvmset_id> — Retrieve the Predictable latency per NVM set log for the given nvmset id. This argument is mandatory, and its success may depend on the device’s statistics to provide this log. For More details see NVM Express 1.4 Spec. Section 5.14.1.10. The default nvmset id to use is 1 for the device. 👑
• -b, --raw-binary — Print the raw Predictable latency per NVM set log buffer to stdout. 📤

🌈 GLOBAL OPTIONS 🌈

These options are defined at the top-level nvme command and are available to this subcommand, bestie:

• --dry-run — Print the command that would be executed, but do not actually execute it. 🫣
• --no-ioctl-probing — Disable probing for 64-bit IOCTL support. 🛑
• --no-retries — Disable retry logic on transient errors. no second chances energy 💀
• -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. ✨
• --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. 🚨
• --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. 🤫
• --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). ⏳
• -v, --verbose — Increase 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. fact-checked and slaying 💅

🔥 EXAMPLES 🔥

• Print the Predictable latency per NVM set log page in a human readable format:

# nvme log predictable-lat /dev/nvme0

• Print the raw Predictable latency per NVM set log to a file:

# nvme log predictable-lat /dev/nvme0 --raw-binary > nvmset_log.raw

It is probably a bad idea to not redirect stdout when using this mode. 🚨 bestie please redirect, i’m begging 😭

👑 NVME 👑

Part of the nvme-user suite. 🫶

---

and that's the page, bestie — NVME-LOG-PREDICTAB(1) from the NVMe manual, dated 10/30/2026. stay iconic, stay hydrated, and may your log pages always parse ✨💜🦋