NVME-PREDICTABLE-L(1)

πŸ’… NVME-PREDICTABLE-LAT-LOG, but make it a group chat

okay so bestie, gather round, because this one's from the nvme manual (yes the whole NVMe fam, hi πŸ‘‹) β€” it's nvme-predictable-lat-log, and before you get attached: it's deprecated. She's still here, she still works, but she's giving "senior who's retiring but keeps showing up to every meeting." πŸŽ€


✨ NAME ✨

nvme-predictable-lat-log β€” send the Predictable latency per NVM set log page request, get the result and the log back. Also: deprecated, bestie, so read the whole thing before you @ me 😭


πŸ¦‹ SYNOPSIS πŸ¦‹

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

🌸 DESCRIPTION 🌸

So like… this is a deprecated alias of nvme-log-predictable-lat(1). The way it exists purely so your little scripts written against nvme-cli versions older than 3.0 don't throw a whole tantrum. The options and behavior are identical β€” only the top-level command name got kept around.

New scripts, though? Use nvme log predictable-lat instead, periodt. πŸ’… This alias prints a deprecation warning on stderr and may be removed in a future release, so don't build a whole personality around her.

For the full option reference, go see nvme-log-predictable-lat(1) β€” she has the whole menu, this one's just the cute little sticker on the door. 🫢


πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

these live at the top-level nvme command and are available to this subcommand. very much "one for all, all for one" energy ngl ✨

  • --dry-run β€” prints the command that would be executed, but doesn't actually execute it. window shopping, but for syscalls πŸ›οΈ
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” disables the retry logic on transient errors. no second chances, she said πŸ’€
  • -o <fmt>, --output-format=<fmt> β€” sets the reporting format to normal, tabular, 'json, or binary. only one output format at a time, don't get greedy πŸ“
  • --output-format-version=<version> β€” picks the output format version. version 1 uses the original field naming, while version 2 (the default, main character energy πŸ‘‘) gives you more consistent and script-friendly field names. any other version? rejected. respectfully, no πŸ™ˆ
  • --quiet β€” suppresses informational messages. errors are still reported (she's quiet, not blind), and --quiet cancels any --verbose for the library log level. they cannot coexist, it's a whole thing 😭
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). literally forever, no cap ⏳
  • -v, --verbose β€” increases the level of detail in the output. you can specify it multiple times to crank the verbosity even further. go off, be nosy πŸ”₯
cute little fact: these options can also be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file β€” the flag wins, every time, no discussion πŸ’…

🧚 EXAMPLES 🧚

No Examples

(yeah. that's it. that's the section. she said "figure it out" 😭)


🌈 NVME 🌈

Part of the nvme-user suite 🫢


⭐ SEE ALSO ⭐


and that's the whole vibe check, bestie! this page came straight from the NVMe manual, dated 10/30/2026 β€” so go forth, use the new command name, and let this deprecated icon live her best retired life πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from