summaryrefslogtreecommitdiffstats
path: root/Documentation/nvme-get-log.txt
blob: d371f5dae57916c09464d4b1201a5a8e07422264 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
nvme-get-log(1)
===============

NAME
----
nvme-get-log - Retrieves a log page from an NVMe device

SYNOPSIS
--------
[verse]
'nvme get-log' <device> [--log-id=<log-id> | -i <log-id>]
                [--log-len=<log-len> | -l <log-len>]
                [--aen=<aen> | -a <aen>]
                [--namespace-id=<nsid> | -n <nsid>]
                [--raw-binary | -b]
                [--lpo=<offset> | -o <offset>]
                [--lsp=<field> | -s <field>]
                [--lsi=<field> | -S <field>]
                [--rae | -r]
                [--csi=<command_set_identifier> | -y <command_set_identifier>]
                [--ot | -O]

DESCRIPTION
-----------
Retrieves an arbitrary NVMe 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 log structure may be returned in one of several
ways depending on the option flags; the structure may be displayed in
hex by the program or the raw buffer may be printed to stdout for another
program to parse.

OPTIONS
-------
-l <log-len>::
--log-len=<log-len>::
	Allocates a buffer of <log-len> bytes size and requests this
	many bytes be returned in the constructed NVMe command. This
	param is mandatory.

-i <log-id>::
--log-id=<log-id>::
	Sets the commands requested log-id to <log-id>. Defaults to 0.

-a <aen>::
--aen=<aen>::
	Convenience field for extracting log information based on an
	asynchronous event notification result. This will override log-id and
	log-len, if set.

-n <nsid>::
--namespace-id=<nsid>::
	Sets the command's nsid value to the given nsid. Defaults to
	0xffffffff if not given. This option may not affect anything
	depending on the log page, which may or may not be specific to
	a namespace.

-b::
--raw-binary::
	Print the raw log buffer to stdout.

-o <offset>::
--lpo=<offset>::
	The log page offset specifies the location within a log page to start
	returning data from. It's Dword-aligned and 64-bits.

-s <field>::
--lsp=<field>::
	The log specified field of LID.

-S <field>::
--lsi=<field>::
	The log specified field of Log Specific Identifier.

-r::
--rae::
	Retain an Asynchronous Event.

-y <command_set_identifier>::
--csi=<command_set_identifier>::
	This field specifies the identifier of command set.
	if not issued, NVM Command Set will be selected.

-O::
--ot::
	Offset Type

EXAMPLES
--------
* Get 512 bytes from log page 2
+
------------
# nvme get-log /dev/nvme0 --log-id=2 --log-len=512
------------
+
The above example will get log page 2 (SMART), and request 512
bytes. On success, the returned log will be dumped in hex and not
interpreted by the program.

* Have the program return the raw log page in binary:
+
------------
# nvme get-log /dev/nvme0 -log-id=2 --log-len=512 --raw-binary > log_page_2.raw
# nvme get-log /dev/nvme0 -i 2 -l 512 -b > log_page_2.raw
------------
+
It is not a good idea to not redirect stdout when using this mode.

NVME
----
Part of the nvme-user suite