NVME-PRED-LAT-EVE(1)

📦
version 3.2 · 14 versions
, in arch rolling

💅 nvme-pred-lat-event-agg-log — predictable latency event aggregate log page, but make it deprecated

okay so real talk, this is a page from the NVMe Manual (yes, the nvme manual, hi bestie 👋), and the star of the show is nvme-pred-lat-event-agg-log. It's giving legacy, it's giving "we kept the old name for you", and honestly? Kind of iconic for that.

✨ NAME ✨

nvme-pred-lat-event-agg-log — send a Predictable Latency Event Aggregate Log Page request, get the result and log back. also, and I cannot stress this enough: deprecated 🫠

🦋 SYNOPSIS 🦋

nvme [<global-options>] pred-lat-event-agg-log <device>
                        [--log-entries=<log_entries> | -e <log_entries>]
                        [--rae | -r] [--raw-binary | -b]

like, that's the whole vibe. <device> goes in, log page comes out 💖

🌸 DESCRIPTION 🌸

So this is a deprecated alias for nvme-log-pred-lat-event-agg(1), and the reason it still exists is literally just for scripts written against nvme-cli versions older than 3.0. That's it. That's the whole reason. We keep it so your ancient script doesn't cry 😭

Options and behavior are identical — the only thing hanging around is the top-level command name itself. Nothing else changed, no cap.

New scripts should use nvme log pred-lat-event-agg instead. This alias prints a deprecation warning on stderr (rude but fair) and may be removed in a future release, so like... don't get attached 🔥

Heads up bestie: for the full option reference, go read nvme-log-pred-lat-event-agg(1). This page is not the one with the full menu.

👑 GLOBAL OPTIONS 👑

The following options are defined at the top-level nvme command and are available to this subcommand. So they're not technically this command's options, they're inherited — nepotism, but make it Unix 💅

  • --dry-run — prints the command that would be executed, but does not actually execute it. it's the "look with your eyes, not your hands" of flags 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. no probing, no drama.
  • --no-retries — disables 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> — selects the output format version. Version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. Any other versions are rejected — no negotiating 🚫
  • --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. they cannot coexist, it's giving enemies to lovers but actually just enemies 💀
  • --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. four keys, that's the whole roster 🎀
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). yes, forever is an option, live your truth ⭐
  • -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack it like a combo, the way that it just keeps going 📈

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. flags beat files, periodt 👑

🍓 EXAMPLES 🍓

No Examples

yeah. that's it. that's the section. no examples. none. zero. the void 🌈

🧚 NVME 🧚

Part of the nvme-user suite 💜

⭐ SEE ALSO ⭐

ok and that's the page!! ngl this one's mostly a "please migrate" note disguised as a manpage, but she served her purpose 🙏

— written under the NVMe name, dated 10/30/2026, and officially titled NVME-PRED-LAT-EVE(1) (yes the header truncates it, they ran out of room, it's fine, we stan a short filename). bye bestie, go use the non-deprecated command 💖🦋✨

📦 where this page comes from