1NVME-ENDURANCE-EVE(1) NVMe Manual NVME-ENDURANCE-EVE(1)
2
3
4
6 nvme-endurance-event-agg-log - Send NVMe Endurance log page request,
7 returns result and log
8
10 nvme endurance-event-agg-log <device> [--log-entries=<log_entries> | -e <log_entries>]
11 [--rae | -r] [--raw-binary | -b]
12 [--output-format=<fmt> | -o <fmt>]
13
15 Retrieves the NVMe Endurance Event Aggregate log page from an NVMe
16 device and provides the returned structure.
17
18 The <device> parameter is mandatory and may be either the NVMe
19 character device (ex: /dev/nvme0), or a namespace block device (ex:
20 /dev/nvme0n1).
21
22 On success, the returned endurance event agg log structure may be
23 returned in one of several ways depending on the option flags; the
24 structure may parsed by the program and printed in a readable format,
25 the raw buffer may be printed to stdout for another program to parse,
26 or reported in json format.
27
29 -e <log_entries>, --log-entries=<log_entries>
30 Retrieve the Endurance Group Event Aggregate Log pending entries.
31 This argument is mandatory and its success may depend on the
32 device’s statistics to provide this log For More details see NVM
33 Express 1.4 Spec. Section 5.14.1.15. The maximum number of log
34 entries supported is 2044 for the device.
35
36 -r, --rae
37 Retain an Asynchronous Event.
38
39 -o <format>, --output-format=<format>
40 Set the reporting format to normal, json, or binary. Only one
41 output format can be used at a time.
42
44 • Print the Endurance log page in a human readable format:
45
46 # nvme endurance-event-agg-log /dev/nvme0
47
48 • Print the raw Endurance log to a file:
49
50 # nvme endurance-event-agg-log /dev/nvme0 --output=binary > endurance_event_agg_log.raw
51
52 It is probably a bad idea to not redirect stdout when using this
53 mode.
54
56 Part of the nvme-user suite
57
58
59
60NVMe 09/29/2023 NVME-ENDURANCE-EVE(1)