From: Keith Busch Date: Mon, 26 Jun 2017 20:00:08 +0000 (-0400) Subject: Regenerate documentation X-Git-Tag: v1.4~39 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=5b44e12c7173ff89bbc66fd72818c8d957119ab0;p=users%2Fsagi%2Fnvme-cli.git Regenerate documentation Signed-off-by: Keith Busch --- diff --git a/Documentation/nvme-admin-passthru.1 b/Documentation/nvme-admin-passthru.1 index 035c88d6..4330d360 100644 --- a/Documentation/nvme-admin-passthru.1 +++ b/Documentation/nvme-admin-passthru.1 @@ -2,12 +2,12 @@ .\" Title: nvme-admin-passthru .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-ADMIN\-PASSTHR" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-ADMIN\-PASSTHR" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-admin-passthru.html b/Documentation/nvme-admin-passthru.html index 3e667264..e74aee00 100644 --- a/Documentation/nvme-admin-passthru.html +++ b/Documentation/nvme-admin-passthru.html @@ -972,7 +972,7 @@ Or if you want to save that structure to a file:
diff --git a/Documentation/nvme-attach-ns.1 b/Documentation/nvme-attach-ns.1 index 14b47559..435823b9 100644 --- a/Documentation/nvme-attach-ns.1 +++ b/Documentation/nvme-attach-ns.1 @@ -2,12 +2,12 @@ .\" Title: nvme-attach-ns .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-ATTACH\-NS" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-ATTACH\-NS" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-attach-ns.html b/Documentation/nvme-attach-ns.html index 2cc7f084..4969f0d1 100644 --- a/Documentation/nvme-attach-ns.html +++ b/Documentation/nvme-attach-ns.html @@ -3,7 +3,7 @@ - + nvme-attach-ns(1) - - - -
-
-

SYNOPSIS

-
-
-
nvme huawei id-ctrl <device> [-v | --vendor-specific] [-b | --raw-binary]
-                        [-o <fmt> | --output-format=<fmt>]
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, sends an identify controller command and -provides the result and 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).

-

This will only work on Huawei devices supporting this feature. -Results for any other device are undefined.

-

On success, the structure may be returned in one of several ways depending -on the option flags; the structure may be parsed by the program or the -raw buffer may be printed to stdout.

-

If having the program decode the output for readability, this version -will decode Huawei vendor unique portions of the structure.

-
-
-
-

OPTIONS

-
-
-
--b -
-
---raw-binary -
-
-

- Print the raw buffer to stdout. Structure is not parsed by - program. This overrides the vendor specific and human readable options. -

-
-
--v -
-
---vendor-specific -
-
-

- In addition to parsing known fields, this option will dump - the vendor specific region of the structure in hex with ascii - interpretation. -

-
-
--H -
-
---human-readable -
-
-

- This option will parse and format many of the bit fields - into human-readable formats. -

-
-
--o <format> -
-
---output-format=<format> -
-
-

- Set the reporting format to normal, json, or - binary. Only one output format can be used at a time. -

-
-
-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Has the program interpret the returned buffer and display the known -fields in a human readable format: -

    -
    -
    -
    # nvme huawei id-ctrl /dev/nvme0
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite

-
-
-
-
- - - + + + + + +nvme-huawei-id-ctrl(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme huawei id-ctrl <device> [-v | --vendor-specific] [-b | --raw-binary]
+                        [-o <fmt> | --output-format=<fmt>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, sends an identify controller command and +provides the result and 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).

+

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

+

On success, the structure may be returned in one of several ways depending +on the option flags; the structure may be parsed by the program or the +raw buffer may be printed to stdout.

+

If having the program decode the output for readability, this version +will decode Huawei vendor unique portions of the structure.

+
+
+
+

OPTIONS

+
+
+
+-b +
+
+--raw-binary +
+
+

+ Print the raw buffer to stdout. Structure is not parsed by + program. This overrides the vendor specific and human readable options. +

+
+
+-v +
+
+--vendor-specific +
+
+

+ In addition to parsing known fields, this option will dump + the vendor specific region of the structure in hex with ascii + interpretation. +

+
+
+-H +
+
+--human-readable +
+
+

+ This option will parse and format many of the bit fields + into human-readable formats. +

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

+ Set the reporting format to normal, json, or + binary. Only one output format can be used at a time. +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program interpret the returned buffer and display the known +fields in a human readable format: +

    +
    +
    +
    # nvme huawei id-ctrl /dev/nvme0
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite

+
+
+
+
+ + + diff --git a/Documentation/nvme-huawei-list.1 b/Documentation/nvme-huawei-list.1 index 131545cb..d87f3980 100644 --- a/Documentation/nvme-huawei-list.1 +++ b/Documentation/nvme-huawei-list.1 @@ -2,12 +2,12 @@ .\" Title: nvme-list .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-LIST" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-LIST" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-huawei-list.html b/Documentation/nvme-huawei-list.html index 425302eb..30b64492 100644 --- a/Documentation/nvme-huawei-list.html +++ b/Documentation/nvme-huawei-list.html @@ -1,806 +1,800 @@ - - - - - -nvme-huawei-list(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme huawei list [-o <fmt> | --output-format=<fmt>]
-
-
-
-
-
-

DESCRIPTION

-
-

Scan the sysfs tree for NVM Express devices and return the /dev node -for those Huawei devices as well as some pertinent information about them.

-
-
-
-

OPTIONS

-
-
-
--o <format> -
-
---output-format=<format> -
-
-

- Set the reporting format to normal or json. Only one output - format can be used at a time. -

-
-
-
-
-
-

EXAMPLES

-
-

No examples yet.

-
-
-
-

NVME

-
-

Part of the nvme-user suite

-
-
-
-
- - - + + + + + +nvme-list(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme huawei list [-o <fmt> | --output-format=<fmt>]
+
+
+
+
+
+

DESCRIPTION

+
+

Scan the sysfs tree for NVM Express devices and return the /dev node +for those Huawei devices as well as some pertinent information about them.

+
+
+
+

OPTIONS

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

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

+
+
+
+
+
+

EXAMPLES

+
+

No examples yet.

+
+
+
+

NVME

+
+

Part of the nvme-user suite

+
+
+
+
+ + + diff --git a/Documentation/nvme-id-ctrl.1 b/Documentation/nvme-id-ctrl.1 index da2d0f44..e6a85938 100644 --- a/Documentation/nvme-id-ctrl.1 +++ b/Documentation/nvme-id-ctrl.1 @@ -2,12 +2,12 @@ .\" Title: nvme-id-ctrl .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-ID\-CTRL" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-ID\-CTRL" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-id-ctrl.html b/Documentation/nvme-id-ctrl.html index 8ee04244..61043216 100644 --- a/Documentation/nvme-id-ctrl.html +++ b/Documentation/nvme-id-ctrl.html @@ -3,7 +3,7 @@ - + nvme-id-ctrl(1) - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc cap-diag <device> [--output-file=<FILE>, -o <FILE>]
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, sends the WDC Vendor Unique Capture-Diagnostics -request and saves the result to a file.

-

The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-
-
-
-

OPTIONS

-
-
-
--o <FILE> -
-
---output-file=<FILE> -
-
-

- Output file; defaults to device serial number followed by "cap_diag" suffix -

-
-
-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Gets the capture diagnostics log from the device and saves to default file in current directory (e.g. STM00019F3F9cap_diag.bin): -

    -
    -
    -
    # nvme wdc cap-diag /dev/nvme0
    -
    -
    • -
  • -

    -Gets the capture diagnostics log from the device and saves to defined file in current directory (e.g. testSTM00019F3F9cap_diag.bin): -

    -
    -
    -
    # nvme wdc cap-diag /dev/nvme0 -o test
    -
    -
    • -
  • -

    -Gets the capture diagnostics log from the device and saves to defined file with pathname (e.g. /tmp/testSTM00019F3F9cap_diag.bin): -

    -
    -
    -
    # nvme wdc cap-diag /dev/nvme0 -o /tmp/test
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite.

-
-
-
-
- - - + + + + + +nvme-wdc-cap-diag(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc cap-diag <device> [--output-file=<FILE>, -o <FILE>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, sends the WDC Vendor Unique Capture-Diagnostics +request and saves the result to a file.

+

The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).

+

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

+
+
+
+

OPTIONS

+
+
+
+-o <FILE> +
+
+--output-file=<FILE> +
+
+

+ Output file; defaults to device serial number followed by "cap_diag" suffix +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Gets the capture diagnostics log from the device and saves to default file in current directory (e.g. STM00019F3F9cap_diag.bin): +

    +
    +
    +
    # nvme wdc cap-diag /dev/nvme0
    +
    +
    • +
  • +

    +Gets the capture diagnostics log from the device and saves to defined file in current directory (e.g. testSTM00019F3F9cap_diag.bin): +

    +
    +
    +
    # nvme wdc cap-diag /dev/nvme0 -o test
    +
    +
    • +
  • +

    +Gets the capture diagnostics log from the device and saves to defined file with pathname (e.g. /tmp/testSTM00019F3F9cap_diag.bin): +

    +
    +
    +
    # nvme wdc cap-diag /dev/nvme0 -o /tmp/test
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite.

+
+
+
+
+ + + diff --git a/Documentation/nvme-wdc-drive-log.1 b/Documentation/nvme-wdc-drive-log.1 index 0f2ac14f..6980a898 100644 --- a/Documentation/nvme-wdc-drive-log.1 +++ b/Documentation/nvme-wdc-drive-log.1 @@ -2,12 +2,12 @@ .\" Title: nvme-wdc-drive-log .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WDC\-DRIVE\-LO" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WDC\-DRIVE\-LO" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-wdc-drive-log.html b/Documentation/nvme-wdc-drive-log.html index 2080ec34..fcca8bcd 100644 --- a/Documentation/nvme-wdc-drive-log.html +++ b/Documentation/nvme-wdc-drive-log.html @@ -1,834 +1,832 @@ - - - - - -nvme-wdc-drive-log(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc drive-log <device> [--output-file=<FILE>, -o <FILE>]
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, sends the wdc vendor unique drive log -request and saves the result to a file.

-

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

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-
-
-
-

OPTIONS

-
-
-
--o <FILE> -
-
---output-file=<FILE> -
-
-

- Output file; defaults to device serial number followed by "drive_log" suffix -

-
-
-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Gets the drive log from the device and saves to default file in current directory (e.g. STM00019F3F9drive_log.bin): -

    -
    -
    -
    # nvme wdc drive-log /dev/nvme0
    -
    -
    • -
  • -

    -Gets the drive log from the device and saves to defined file in current directory (e.g. testSTM00019F3F9drive_log.bin): -

    -
    -
    -
    # nvme wdc drive-log /dev/nvme0 -o test
    -
    -
    • -
  • -

    -Gets the drive log from the device and saves to defined file with pathname (e.g. /tmp/testSTM00019F3F9drive_log.bin): -

    -
    -
    -
    # nvme wdc drive-log /dev/nvme0 -o /tmp/test
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite

-
-
-
-
- - - + + + + + +nvme-wdc-drive-log(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc drive-log <device> [--output-file=<FILE>, -o <FILE>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, sends the wdc vendor unique drive log +request and saves the result to a file.

+

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

+

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

+
+
+
+

OPTIONS

+
+
+
+-o <FILE> +
+
+--output-file=<FILE> +
+
+

+ Output file; defaults to device serial number followed by "drive_log" suffix +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Gets the drive log from the device and saves to default file in current directory (e.g. STM00019F3F9drive_log.bin): +

    +
    +
    +
    # nvme wdc drive-log /dev/nvme0
    +
    +
    • +
  • +

    +Gets the drive log from the device and saves to defined file in current directory (e.g. testSTM00019F3F9drive_log.bin): +

    +
    +
    +
    # nvme wdc drive-log /dev/nvme0 -o test
    +
    +
    • +
  • +

    +Gets the drive log from the device and saves to defined file with pathname (e.g. /tmp/testSTM00019F3F9drive_log.bin): +

    +
    +
    +
    # nvme wdc drive-log /dev/nvme0 -o /tmp/test
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite

+
+
+
+
+ + + diff --git a/Documentation/nvme-wdc-get-crash-dump.1 b/Documentation/nvme-wdc-get-crash-dump.1 index 0d587a56..d15831b1 100644 --- a/Documentation/nvme-wdc-get-crash-dump.1 +++ b/Documentation/nvme-wdc-get-crash-dump.1 @@ -2,12 +2,12 @@ .\" Title: nvme-wdc-get-crash-dump .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WDC\-GET\-CRAS" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WDC\-GET\-CRAS" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-wdc-get-crash-dump.html b/Documentation/nvme-wdc-get-crash-dump.html index c2ab0658..66bcf33d 100644 --- a/Documentation/nvme-wdc-get-crash-dump.html +++ b/Documentation/nvme-wdc-get-crash-dump.html @@ -1,835 +1,833 @@ - - - - - -nvme-wdc-get-crash-dump(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc get-crash-dump <device> [--output-file=<FILE>, -o <FILE>]
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, sends the WDC vendor unique crash dump -request and saves the result to file. In current implementation crash dump is -captured if it is present. On success it will save the dump in file with -appropriate suffix. Note that this command will clear the available -dump from the device on success.

-

The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-
-
-
-

OPTIONS

-
-
-
--o <FILE> -
-
---output-file=<FILE> -
-
-

- Output file; defaults to device serial number followed by "crash_dump" suffix -

-
-
-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Gets the crash dump from the device and saves to default file in current directory (e.g. STM00019F3F9crash_dump.bin): -

    -
    -
    -
    # nvme wdc get-crash-dump /dev/nvme0
    -
    -
    • -
  • -

    -Gets the crash dump from the device and saves to defined file in current directory (e.g. testSTM00019F3F9crash_dump.bin): -

    -
    -
    -
    # nvme wdc get-crash-dump /dev/nvme0 -o test
    -
    -
    • -
  • -

    -Gets the crash dump from the device and saves to defined file with pathname (e.g. /tmp/testSTM00019F3F9crash_dump.bin): -

    -
    -
    -
    # nvme wdc get-crash-dump /dev/nvme0 -o /tmp/test
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite

-
-
-
-
- - - + + + + + +nvme-wdc-get-crash-dump(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc get-crash-dump <device> [--output-file=<FILE>, -o <FILE>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, sends the WDC vendor unique crash dump +request and saves the result to file. In current implementation crash dump is +captured if it is present. On success it will save the dump in file with +appropriate suffix. Note that this command will clear the available +dump from the device on success.

+

The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).

+

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

+
+
+
+

OPTIONS

+
+
+
+-o <FILE> +
+
+--output-file=<FILE> +
+
+

+ Output file; defaults to device serial number followed by "crash_dump" suffix +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Gets the crash dump from the device and saves to default file in current directory (e.g. STM00019F3F9crash_dump.bin): +

    +
    +
    +
    # nvme wdc get-crash-dump /dev/nvme0
    +
    +
    • +
  • +

    +Gets the crash dump from the device and saves to defined file in current directory (e.g. testSTM00019F3F9crash_dump.bin): +

    +
    +
    +
    # nvme wdc get-crash-dump /dev/nvme0 -o test
    +
    +
    • +
  • +

    +Gets the crash dump from the device and saves to defined file with pathname (e.g. /tmp/testSTM00019F3F9crash_dump.bin): +

    +
    +
    +
    # nvme wdc get-crash-dump /dev/nvme0 -o /tmp/test
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite

+
+
+
+
+ + + diff --git a/Documentation/nvme-wdc-id-ctrl.1 b/Documentation/nvme-wdc-id-ctrl.1 index b4c191fb..305afe89 100644 --- a/Documentation/nvme-wdc-id-ctrl.1 +++ b/Documentation/nvme-wdc-id-ctrl.1 @@ -2,12 +2,12 @@ .\" Title: nvme-wdc-id-ctrl .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WDC\-ID\-CTRL" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WDC\-ID\-CTRL" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-wdc-id-ctrl.html b/Documentation/nvme-wdc-id-ctrl.html index fe68d69b..dbbe29e7 100644 --- a/Documentation/nvme-wdc-id-ctrl.html +++ b/Documentation/nvme-wdc-id-ctrl.html @@ -1,860 +1,858 @@ - - - - - -nvme-wdc-id-ctrl(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc id-ctrl <device> [-v | --vendor-specific] [-b | --raw-binary]
-                        [-o <fmt> | --output-format=<fmt>]
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, sends an identify controller command and -provides the result and 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).

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-

On success, the structure may be returned in one of several ways depending -on the option flags; the structure may be parsed by the program or the -raw buffer may be printed to stdout.

-

If having the program decode the output for readability, this version -will decode WDC vendor unique portions of the structure.

-
-
-
-

OPTIONS

-
-
-
--b -
-
---raw-binary -
-
-

- Print the raw buffer to stdout. Structure is not parsed by - program. This overrides the vendor specific and human readable options. -

-
-
--v -
-
---vendor-specific -
-
-

- In addition to parsing known fields, this option will dump - the vendor specific region of the structure in hex with ascii - interpretation. -

-
-
--H -
-
---human-readable -
-
-

- This option will parse and format many of the bit fields - into human-readable formats. -

-
-
--o <format> -
-
---output-format=<format> -
-
-

- Set the reporting format to normal, json, or - binary. Only one output format can be used at a time. -

-
-
-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Has the program interpret the returned buffer and display the known -fields in a human readable format: -

    -
    -
    -
    # nvme wdc id-ctrl /dev/nvme0
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite

-
-
-
-
- - - + + + + + +nvme-wdc-id-ctrl(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc id-ctrl <device> [-v | --vendor-specific] [-b | --raw-binary]
+                        [-o <fmt> | --output-format=<fmt>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, sends an identify controller command and +provides the result and 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).

+

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

+

On success, the structure may be returned in one of several ways depending +on the option flags; the structure may be parsed by the program or the +raw buffer may be printed to stdout.

+

If having the program decode the output for readability, this version +will decode WDC vendor unique portions of the structure.

+
+
+
+

OPTIONS

+
+
+
+-b +
+
+--raw-binary +
+
+

+ Print the raw buffer to stdout. Structure is not parsed by + program. This overrides the vendor specific and human readable options. +

+
+
+-v +
+
+--vendor-specific +
+
+

+ In addition to parsing known fields, this option will dump + the vendor specific region of the structure in hex with ascii + interpretation. +

+
+
+-H +
+
+--human-readable +
+
+

+ This option will parse and format many of the bit fields + into human-readable formats. +

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

+ Set the reporting format to normal, json, or + binary. Only one output format can be used at a time. +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program interpret the returned buffer and display the known +fields in a human readable format: +

    +
    +
    +
    # nvme wdc id-ctrl /dev/nvme0
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite

+
+
+
+
+ + + diff --git a/Documentation/nvme-wdc-purge-monitor.1 b/Documentation/nvme-wdc-purge-monitor.1 index a36e7055..ebe87c13 100644 --- a/Documentation/nvme-wdc-purge-monitor.1 +++ b/Documentation/nvme-wdc-purge-monitor.1 @@ -2,12 +2,12 @@ .\" Title: nvme-wdc-purge-monitor .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WDC\-PURGE\-MO" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WDC\-PURGE\-MO" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-wdc-purge-monitor.html b/Documentation/nvme-wdc-purge-monitor.html index c8ef8ea3..d17e87fd 100644 --- a/Documentation/nvme-wdc-purge-monitor.html +++ b/Documentation/nvme-wdc-purge-monitor.html @@ -1,842 +1,840 @@ - - - - - -nvme-wdc-purge-monitor(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc purge-monitor <device>
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, send a Vendor Unique WDC Purge-Monitor command and -provide the status of the purge command.

-

Expected status and description :-

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Status Code Description

0x00

Purge State Idle.

0x01

Purge State Done.

0x02

Purge State Busy.

0x03

Purge State Error : Purge operation resulted in error, power cycle required.

0x04

Purge State Error : Purge operation interrupted by power cycle or reset.

-
-

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

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-

On success it returns 0, error code otherwise.

-
-
-
-

OPTIONS

-
-

No options yet.

-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Has the program issue WDC Purge-Monitor Vendor Unique Command : -

    -
    -
    -
    # nvme wdc purge-monitor /dev/nvme0
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite.

-
-
-
-
- - - + + + + + +nvme-wdc-purge-monitor(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc purge-monitor <device>
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, send a Vendor Unique WDC Purge-Monitor command and +provide the status of the purge command.

+

Expected status and description :-

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Status Code Description

0x00

Purge State Idle.

0x01

Purge State Done.

0x02

Purge State Busy.

0x03

Purge State Error : Purge operation resulted in error, power cycle required.

0x04

Purge State Error : Purge operation interrupted by power cycle or reset.

+
+

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

+

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

+

On success it returns 0, error code otherwise.

+
+
+
+

OPTIONS

+
+

No options yet.

+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program issue WDC Purge-Monitor Vendor Unique Command : +

    +
    +
    +
    # nvme wdc purge-monitor /dev/nvme0
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite.

+
+
+
+
+ + + diff --git a/Documentation/nvme-wdc-purge.1 b/Documentation/nvme-wdc-purge.1 index f56c5e02..f7c8a2d0 100644 --- a/Documentation/nvme-wdc-purge.1 +++ b/Documentation/nvme-wdc-purge.1 @@ -2,12 +2,12 @@ .\" Title: nvme-wdc-purge .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WDC\-PURGE" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WDC\-PURGE" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-wdc-purge.html b/Documentation/nvme-wdc-purge.html index 03935656..e4fd6e89 100644 --- a/Documentation/nvme-wdc-purge.html +++ b/Documentation/nvme-wdc-purge.html @@ -1,804 +1,802 @@ - - - - - -nvme-wdc-purge(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc purge <device>
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, sends a Vendor Unique WDC Purge command and -provides the result.

-

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

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-

On success it returns 0, error code otherwise.

-
-
-
-

OPTIONS

-
-

No options yet.

-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Has the program issue WDC Purge Vendor Unique Command : -

    -
    -
    -
    # nvme wdc purge /dev/nvme0n1
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite.

-
-
-
-
- - - + + + + + +nvme-wdc-purge(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc purge <device>
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, sends a Vendor Unique WDC Purge command and +provides the result.

+

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

+

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

+

On success it returns 0, error code otherwise.

+
+
+
+

OPTIONS

+
+

No options yet.

+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program issue WDC Purge Vendor Unique Command : +

    +
    +
    +
    # nvme wdc purge /dev/nvme0n1
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite.

+
+
+
+
+ + + diff --git a/Documentation/nvme-wdc-smart-log-add.1 b/Documentation/nvme-wdc-smart-log-add.1 index 5363d815..e70109d4 100644 --- a/Documentation/nvme-wdc-smart-log-add.1 +++ b/Documentation/nvme-wdc-smart-log-add.1 @@ -2,12 +2,12 @@ .\" Title: nvme-wdc-smart-log-add .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WDC\-SMART\-LO" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WDC\-SMART\-LO" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-wdc-smart-log-add.html b/Documentation/nvme-wdc-smart-log-add.html index e5790560..9698063c 100644 --- a/Documentation/nvme-wdc-smart-log-add.html +++ b/Documentation/nvme-wdc-smart-log-add.html @@ -1,1028 +1,1026 @@ - - - - - -nvme-wdc-smart-log-add(1) - - - - - -
-
-

SYNOPSIS

-
-
-
nvme wdc smart-log-add <device> [--interval=<NUM>, -i <NUM>] [--output-format=<normal|json> -o <normal|json>]
-
-
-
-
-
-

DESCRIPTION

-
-

For the NVMe device given, send a Vendor Unique WDC smart-log-add command and -provide the additional smart log. The --interval option will return performance -statistics from the specified reporting interval.

-

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

-

This will only work on WDC devices supporting this feature. -Results for any other device are undefined.

-

On success it returns 0, error code otherwise.

-
-
-
-

OPTIONS

-
-
-
--i <NUM> -
-
---interval=<NUM> -
-
-

- Return the statistics from specific interval, defaults to 14 -

-
-
--o <format> -
-
---output-format=<format> -
-
-

- Set the reporting format to human, or - json. Only one output format can be used at a time. - Default is human. -

-
-
-

Valid Interval values and description :-

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Value Description

1

Most recent five (5) minute accumulated set.

2-12

Previous five (5) minute accumulated sets.

13

The accumulated total of sets 1 through 12 that contain the previous hour of -accumulated statistics.

14

The statistical set accumulated since power-up.

15

The statistical set accumulated during the entire lifetime of the device.

-
-
-
-
-

Output Explanation

-
-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Field Description

Host Read Commands

Number of host read commands received during the reporting period.

Host Read Blocks

Number of 512-byte blocks requested during the reporting period.

Average Read Size

Average Read size is calculated using (Host Read Blocks/Host Read Commands).

Host Read Cache Hit Commands

Number of host read commands that serviced entirely from the on-board read -cache during the reporting period. No access to the NAND flash memory was required. -This count is only updated if the entire command was serviced from the cache memory.

Host Read Cache Hit Percentage

Percentage of host read commands satisfied from the cache.

Host Read Cache Hit Blocks

Number of 512-byte blocks of data that have been returned for Host Read Cache Hit -Commands during the reporting period. This count is only updated with the blocks -returned for host read commands that were serviced entirely from cache memory.

Average Read Cache Hit Size

Average size of read commands satisfied from the cache.

Host Read Commands Stalled

Number of host read commands that were stalled due to a lack of resources within -the SSD during the reporting period (NAND flash command queue full, low cache page count, -cache page contention, etc.). Commands are not considered stalled if the only reason for -the delay was waiting for the data to be physically read from the NAND flash. It is normal -to expect this count to equal zero on heavily utilized systems.

Host Read Commands Stalled Percentage

Percentage of read commands that were stalled. If the figure is consistently high, -then consideration should be given to spreading the data across multiple SSDs.

Host Write Commands

Number of host write commands received during the reporting period.

Host Write Blocks

Number of 512-byte blocks written during the reporting period.

Average Write Size

Average Write size calculated using (Host Write Blocks/Host Write Commands).

Host Write Odd Start Commands

Number of host write commands that started on a non-aligned boundary during -the reporting period. The size of the boundary alignment is normally 4K; therefore -this returns the number of commands that started on a non-4K aligned boundary. -The SSD requires slightly more time to process non-aligned write commands than it -does to process aligned write commands.

Host Write Odd Start Commands Percentage

Percentage of host write commands that started on a non-aligned boundary. If this -figure is equal to or near 100%, and the NAND Read Before Write value is also high, -then the user should investigate the possibility of offsetting the file system. For -Microsoft Windows systems, the user can use Diskpart. For Unix-based operating systems, -there is normally a method whereby file system partitions can be placed where required.

Host Write Odd End Commands

Number of host write commands that ended on a non-aligned boundary during the -reporting period. The size of the boundary alignment is normally 4K; therefore this -returns the number of commands that ended on a non-4K aligned boundary.

Host Write Odd End Commands Percentage

Percentage of host write commands that ended on a non-aligned boundary.

Host Write Commands Stalled

Number of host write commands that were stalled due to a lack of resources within the -SSD during the reporting period. The most likely cause is that the write data was being -received faster than it could be saved to the NAND flash memory. If there was a large -volume of read commands being processed simultaneously, then other causes might include -the NAND flash command queue being full, low cache page count, or cache page contention, etc. -It is normal to expect this count to be non-zero on heavily utilized systems.

Host Write Commands Stalled Percentage

Percentage of write commands that were stalled. If the figure is consistently high, then -consideration should be given to spreading the data across multiple SSDs.

NAND Read Commands

Number of read commands issued to the NAND devices during the reporting period. -This figure will normally be much higher than the host read commands figure, as the data -needed to satisfy a single host read command may be spread across several NAND flash devices.

NAND Read Blocks

Number of 512-byte blocks requested from NAND flash devices during the reporting period. -This figure would normally be about the same as the host read blocks figure

Average NAND Read Size

Average size of NAND read commands.

NAND Write Commands

Number of write commands issued to the NAND devices during the reporting period. -There is no real correlation between the number of host write commands issued and the -number of NAND Write Commands.

NAND Write Blocks

Number of 512-byte blocks written to the NAND flash devices during the reporting period. -This figure would normally be about the same as the host write blocks figure.

Average NAND Write Size

Average size of NAND write commands. This figure should never be greater than 128K, as -this is the maximum size write that is ever issued to a NAND device.

NAND Read Before Write

This is the number of read before write operations that were required to process -non-aligned host write commands during the reporting period. See Host Write Odd Start -Commands and Host Write Odd End Commands. NAND Read Before Write operations have -a detrimental effect on the overall performance of the device.

-
-
-
-
-

EXAMPLES

-
-
    -
  • -

    -Has the program issue WDC smart-log-add Vendor Unique Command with default interval (14) : -

    -
    -
    -
    # nvme wdc smart-log-add /dev/nvme0
    -
    -
    • -
-
-
-
-

NVME

-
-

Part of the nvme-user suite.

-
-
-
-
- - - + + + + + +nvme-wdc-smart-log-add(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc smart-log-add <device> [--interval=<NUM>, -i <NUM>] [--output-format=<normal|json> -o <normal|json>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, send a Vendor Unique WDC smart-log-add command and +provide the additional smart log. The --interval option will return performance +statistics from the specified reporting interval.

+

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

+

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

+

On success it returns 0, error code otherwise.

+
+
+
+

OPTIONS

+
+
+
+-i <NUM> +
+
+--interval=<NUM> +
+
+

+ Return the statistics from specific interval, defaults to 14 +

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

+ Set the reporting format to human, or + json. Only one output format can be used at a time. + Default is human. +

+
+
+

Valid Interval values and description :-

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Value Description

1

Most recent five (5) minute accumulated set.

2-12

Previous five (5) minute accumulated sets.

13

The accumulated total of sets 1 through 12 that contain the previous hour of +accumulated statistics.

14

The statistical set accumulated since power-up.

15

The statistical set accumulated during the entire lifetime of the device.

+
+
+
+
+

Output Explanation

+
+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Field Description

Host Read Commands

Number of host read commands received during the reporting period.

Host Read Blocks

Number of 512-byte blocks requested during the reporting period.

Average Read Size

Average Read size is calculated using (Host Read Blocks/Host Read Commands).

Host Read Cache Hit Commands

Number of host read commands that serviced entirely from the on-board read +cache during the reporting period. No access to the NAND flash memory was required. +This count is only updated if the entire command was serviced from the cache memory.

Host Read Cache Hit Percentage

Percentage of host read commands satisfied from the cache.

Host Read Cache Hit Blocks

Number of 512-byte blocks of data that have been returned for Host Read Cache Hit +Commands during the reporting period. This count is only updated with the blocks +returned for host read commands that were serviced entirely from cache memory.

Average Read Cache Hit Size

Average size of read commands satisfied from the cache.

Host Read Commands Stalled

Number of host read commands that were stalled due to a lack of resources within +the SSD during the reporting period (NAND flash command queue full, low cache page count, +cache page contention, etc.). Commands are not considered stalled if the only reason for +the delay was waiting for the data to be physically read from the NAND flash. It is normal +to expect this count to equal zero on heavily utilized systems.

Host Read Commands Stalled Percentage

Percentage of read commands that were stalled. If the figure is consistently high, +then consideration should be given to spreading the data across multiple SSDs.

Host Write Commands

Number of host write commands received during the reporting period.

Host Write Blocks

Number of 512-byte blocks written during the reporting period.

Average Write Size

Average Write size calculated using (Host Write Blocks/Host Write Commands).

Host Write Odd Start Commands

Number of host write commands that started on a non-aligned boundary during +the reporting period. The size of the boundary alignment is normally 4K; therefore +this returns the number of commands that started on a non-4K aligned boundary. +The SSD requires slightly more time to process non-aligned write commands than it +does to process aligned write commands.

Host Write Odd Start Commands Percentage

Percentage of host write commands that started on a non-aligned boundary. If this +figure is equal to or near 100%, and the NAND Read Before Write value is also high, +then the user should investigate the possibility of offsetting the file system. For +Microsoft Windows systems, the user can use Diskpart. For Unix-based operating systems, +there is normally a method whereby file system partitions can be placed where required.

Host Write Odd End Commands

Number of host write commands that ended on a non-aligned boundary during the +reporting period. The size of the boundary alignment is normally 4K; therefore this +returns the number of commands that ended on a non-4K aligned boundary.

Host Write Odd End Commands Percentage

Percentage of host write commands that ended on a non-aligned boundary.

Host Write Commands Stalled

Number of host write commands that were stalled due to a lack of resources within the +SSD during the reporting period. The most likely cause is that the write data was being +received faster than it could be saved to the NAND flash memory. If there was a large +volume of read commands being processed simultaneously, then other causes might include +the NAND flash command queue being full, low cache page count, or cache page contention, etc. +It is normal to expect this count to be non-zero on heavily utilized systems.

Host Write Commands Stalled Percentage

Percentage of write commands that were stalled. If the figure is consistently high, then +consideration should be given to spreading the data across multiple SSDs.

NAND Read Commands

Number of read commands issued to the NAND devices during the reporting period. +This figure will normally be much higher than the host read commands figure, as the data +needed to satisfy a single host read command may be spread across several NAND flash devices.

NAND Read Blocks

Number of 512-byte blocks requested from NAND flash devices during the reporting period. +This figure would normally be about the same as the host read blocks figure

Average NAND Read Size

Average size of NAND read commands.

NAND Write Commands

Number of write commands issued to the NAND devices during the reporting period. +There is no real correlation between the number of host write commands issued and the +number of NAND Write Commands.

NAND Write Blocks

Number of 512-byte blocks written to the NAND flash devices during the reporting period. +This figure would normally be about the same as the host write blocks figure.

Average NAND Write Size

Average size of NAND write commands. This figure should never be greater than 128K, as +this is the maximum size write that is ever issued to a NAND device.

NAND Read Before Write

This is the number of read before write operations that were required to process +non-aligned host write commands during the reporting period. See Host Write Odd Start +Commands and Host Write Odd End Commands. NAND Read Before Write operations have +a detrimental effect on the overall performance of the device.

+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program issue WDC smart-log-add Vendor Unique Command with default interval (14) : +

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

NVME

+
+

Part of the nvme-user suite.

+
+
+
+
+ + + diff --git a/Documentation/nvme-write-uncor.1 b/Documentation/nvme-write-uncor.1 index 3047c827..5de6ebe5 100644 --- a/Documentation/nvme-write-uncor.1 +++ b/Documentation/nvme-write-uncor.1 @@ -2,12 +2,12 @@ .\" Title: nvme-uncor .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-UNCOR" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-UNCOR" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-write-uncor.html b/Documentation/nvme-write-uncor.html index 56683e33..1f964f9e 100644 --- a/Documentation/nvme-write-uncor.html +++ b/Documentation/nvme-write-uncor.html @@ -816,7 +816,7 @@ blocks.

diff --git a/Documentation/nvme-write-zeroes.1 b/Documentation/nvme-write-zeroes.1 index acee999f..520b636e 100644 --- a/Documentation/nvme-write-zeroes.1 +++ b/Documentation/nvme-write-zeroes.1 @@ -2,12 +2,12 @@ .\" Title: nvme-zeroes .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-ZEROES" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-ZEROES" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-write-zeroes.html b/Documentation/nvme-write-zeroes.html index b83fc1c3..3fba6179 100644 --- a/Documentation/nvme-write-zeroes.html +++ b/Documentation/nvme-write-zeroes.html @@ -921,7 +921,7 @@ NVME
diff --git a/Documentation/nvme-write.1 b/Documentation/nvme-write.1 index 7f8d89e3..ce131712 100644 --- a/Documentation/nvme-write.1 +++ b/Documentation/nvme-write.1 @@ -2,12 +2,12 @@ .\" Title: nvme-write .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME\-WRITE" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME\-WRITE" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme-write.html b/Documentation/nvme-write.html index bcaf9287..b2e6622c 100644 --- a/Documentation/nvme-write.html +++ b/Documentation/nvme-write.html @@ -976,7 +976,7 @@ metadata is passes.

diff --git a/Documentation/nvme.1 b/Documentation/nvme.1 index 4253afb7..5a38a22e 100644 --- a/Documentation/nvme.1 +++ b/Documentation/nvme.1 @@ -2,12 +2,12 @@ .\" Title: nvme .\" Author: [see the "Authors" section] .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 05/18/2017 +.\" Date: 06/26/2017 .\" Manual: NVMe Manual .\" Source: NVMe .\" Language: English .\" -.TH "NVME" "1" "05/18/2017" "NVMe" "NVMe Manual" +.TH "NVME" "1" "06/26/2017" "NVMe" "NVMe Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/Documentation/nvme.html b/Documentation/nvme.html index 64861224..6da148e7 100644 --- a/Documentation/nvme.html +++ b/Documentation/nvme.html @@ -1115,7 +1115,7 @@ NVM-Express Site.