NVME-LOG-ENDURANCE(1)

📦 version 3.2, in arch rolling

NVME-LOG-ENDURANCE(1) ✨

okay so bestie, welcome to the NVMe Manual page for nvme-log-endurance-event-agg — yes that's a whole mouthful, but it's giving "important little log command" and honestly? iconic. 💅

NAME

nvme-log-endurance-event-agg — send an NVMe Endurance log page request, get the result and the log back. that's it, that's the whole vibe. 🦋

SYNOPSIS

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

look at her. so structured. so slay. 🌸

DESCRIPTION

so what does she actually do? she retrieves the NVMe Endurance Event Aggregate log page from an NVMe device and hands you back the returned structure. literally that simple, no cap. 🎀

the <device> parameter is mandatory — you cannot skip her, she's the main character — and it can be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). either one is fine, pick your fighter. 🙈

on success, that returned endurance event agg log structure can come back in one of several ways depending on your option flags, and there's a whole little menu of formats:

  • the structure may be parsed by the program and printed in a readable format (the cozy option 💖)
  • the raw buffer may be printed to stdout so another program can parse it (the "hand it off to your friend" option 🔥)
  • or it gets reported in json format (the "script girlies rise" option ✨)

OPTIONS

  • -e <log_entries>, --log-entries=<log_entries> — retrieve the Endurance Group Event Aggregate Log pending entries. this argument is mandatory (yes, required, don't forget her 😭) 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.15. also, the maximum number of log entries supported is 2044 for the device — so like, 2044 is the ceiling, bestie, don't push past it. 💀
  • -r, --rae — Retain an Asynchronous Event. that's the whole description, she's short and mysterious and we respect it. 👑

GLOBAL OPTIONS

these ones live at the top-level nvme command and are available to this subcommand too — so they're like, the family options. everyone shares. 🫶

  • --dry-run — print the command that would be executed, but don't actually execute it. a little dress rehearsal, no 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 — you can't have all four, that's greedy. 🍓
  • --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 — sorry babe, we don't do that here. 🙅‍♀️
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she's a "shhh" button but not a "hide the problems" button. 💜
  • --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). basically "wait forever" is a valid mood. 😭
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity — so -v, -vv, -vvv, go off. 🔥
also!! these options can be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. flag supremacy, periodt. 👑

EXAMPLES

  • print the Endurance log page in a human readable format:
# nvme log endurance-event-agg /dev/nvme0
  • print the raw Endurance log to a file:
# nvme log endurance-event-agg /dev/nvme0 --output=binary > endurance_event_agg_log.raw
⚠️ it is probably a bad idea to not redirect stdout when using this mode. like fr fr, don't just let that raw binary spill onto your terminal and act surprised. redirect it. 🙈

NVME

part of the nvme-user suite. one of the family. 🌈

and that's the whole page, bestie!! 💖 this one's from the NVMe Manual, dated <highlight>10/30/2026</highlight>, and it signs off as NVMe / NVME-LOG-ENDURANCE(1) — mwah, go get that endurance log. 💅✨🎀

📦 where this page comes from