1. Manuals
  2. Tumbleweed
  3. nvme-cli
  4. nvme-lba-status-log(1)

Scroll to navigation

NVME-LBA-STATUS-L(1) NVMe Manual NVME-LBA-STATUS-L(1)

NAME

nvme-lba-status-log - Send LBA Status Log Page request returns result and log

SYNOPSIS

nvme [<global-options>] lba-status-log <device> [--rae | -r]

DESCRIPTION

Retrieves the NVMe LBA Status 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 LBA Status Log Page 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

-r, --rae

Retain an Asynchronous Event.

GLOBAL OPTIONS

The following options are defined at the top-level nvme command and are available to this subcommand:

--dry-run

Print the command that would be executed, but do not actually execute it.

--no-ioctl-probing

Disable probing for 64-bit IOCTL support.

--no-retries

Disable retry logic on transient errors.

-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.

--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.

--timeout=<ms>

Set the timeout for the command in milliseconds.

-v, --verbose

Increase the level of detail in the output. May be specified multiple times to further increase verbosity.

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

EXAMPLES

•Print the LBA Status Log page in a normal readable format: 

# nvme lba-status-log /dev/nvme0

•Show the output in json format 

# nvme lba-status-log /dev/nvme0 -o json
+
NVME

Part of the nvme-user suite

07/31/2026 NVMe