From f26f66d866ba1a9f3204e6fdfe2b07e67b5492ad Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 10 Apr 2024 21:41:32 +0200 Subject: Adding upstream version 2.8. Signed-off-by: Daniel Baumann --- Documentation/nvme-ocp-smart-add-log.html | 819 ++++++++++++++++++++++++++++++ 1 file changed, 819 insertions(+) create mode 100644 Documentation/nvme-ocp-smart-add-log.html (limited to 'Documentation/nvme-ocp-smart-add-log.html') diff --git a/Documentation/nvme-ocp-smart-add-log.html b/Documentation/nvme-ocp-smart-add-log.html new file mode 100644 index 0000000..fa10b95 --- /dev/null +++ b/Documentation/nvme-ocp-smart-add-log.html @@ -0,0 +1,819 @@ + + + + + + +nvme-ocp-smart-add-log(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme ocp smart-add-log <device> [--output-format=<fmt> | -o <fmt>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, send a smart-add-log command and +provide the additional smart log.

+

The <device> parameter is mandatory and may be either the NVMe character +device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).

+

This will only work on OCP compliant devices supporting this feature. +Results for any other device are undefined.

+

On success it returns 0, error code otherwise.

+
+
+
+

OPTIONS

+
+
+
+-o <fmt> +
+
+--output-format=<fmt> +
+
+

+ Set the reporting format to normal or json. Only one output format + can be used at a time. The default is normal. +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program issue a smart-add-log command to retrieve the 0xC0 log page. +

    +
    +
    +
    # nvme ocp smart-add-log /dev/nvme0
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite.

+
+
+
+
+ + + -- cgit v1.2.3