blob: 57a13694e37120d9b577d1cbb45eaff8d7b0bbc2 (
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
|
nvme-effects-log(1)
===================
NAME
----
nvme-effects-log - Send NVMe Command Effects log page request, returns result
and log
SYNOPSIS
--------
[verse]
'nvme effects-log' <device> [--human-readable | -H] [--raw-binary | -b]
[--output-format=<fmt> | -o <fmt>] [--verbose | -v]
DESCRIPTION
-----------
Retrieves the NVMe Command Effects log page from an NVMe device and provides
the returned structure.
The <device> parameter is mandatory and should be the NVMe character
device (ex: /dev/nvme0).
On success, the returned command effects log structure will be printed
for each command that is supported.
OPTIONS
-------
-H::
--human-readable::
This option will parse and format many of the bit fields into a
human-readable format.
-b::
--raw-binary::
This option will print the raw buffer to stdout. Structure is not
parsed by program. This overrides the human-readable option.
-o <fmt>::
--output-format=<fmt>::
Set the reporting format to 'normal', 'json' or 'binary'. Only one
output format can be used at a time.
-v::
--verbose::
Increase the information detail in the output.
EXAMPLES
--------
* Print the effects log page in a human readable format:
+
------------
# nvme effects-log /dev/nvme0
------------
+
* Have the program return the raw structure in binary:
+
------------
# nvme effects-log /dev/nvme0 --raw-binary > effects_log.raw
# nvme effects-log /dev/nvme0 -b > effects_log.raw
------------
NVME
----
Part of the nvme-user suite
|
