| NVME-OCP-PERSISTEN(1) | NVMe Manual | NVME-OCP-PERSISTEN(1) |
NAME
nvme-ocp-persistent-event-log - Send NVMe persistent event log page request, returns result and log additional OCP-specific data
SYNOPSIS
nvme [<global-options>] ocp persistent-event-log <device>
[--action=<action> | -a <action>]
[--log-len=<log-len> | -l <log-len>]
[--raw-binary | -b]
DESCRIPTION
Retrieves the NVMe persistent event log page from an NVMe device and provides the returned structure.
The <device> parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1).
On success, the returned persistent event log structure may be returned in one of several ways depending on the option flags; the structure may parsed by the program and printed in a readable format or the raw buffer may be printed to stdout for another program to parse.
OPTIONS
-a <action>, --action=<action>
-l <log-len>, --log-len=<log-len>
-b, --raw-binary
GLOBAL OPTIONS
The following options are defined at the top-level nvme command and are available to this subcommand:
--dry-run
--no-ioctl-probing
--no-retries
-o <fmt>, --output-format=<fmt>
--output-format-version=<version>
--timeout=<ms>
-v, --verbose
These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file.
EXAMPLES
# nvme ocp persistent-event-log /dev/nvme0
# nvme ocp persistent-event-log /dev/nvme0 --raw-binary > persistent_log.raw
It is probably a bad idea to not redirect stdout when using this mode.
NVME
Part of the nvme-user suite
| 09/07/2026 | NVMe |