blob: d3c01040a9ee0e2ffc5c63070a7c5e9914ba0731 (
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
|
nvme-toshiba-vs-internal-log(1)
===============================
NAME
----
nvme-toshiba-vs-internal-log - Retrieve a Toshiba device's vendor specific internal log and either save to file or dump the contents.
SYNOPSIS
--------
[verse]
'nvme toshiba vs-internal-log ' <device>
[--output-file=<FILE>, -o <FILE>] (optional)
[--saved-log, -s] (optional)
DESCRIPTION
-----------
For the NVMe device given, sends the Toshiba internal device log
request and either saves the result to a file or dumps the content to stdout.
The <device> parameter is mandatory and may be either the NVMe
character device (ex: /dev/nvme0), or a namespace block device (ex:
/dev/nvme0n1).
The log is associated with the controller rather than any
namespaces.
Two logs exist, the current log and the previous log.
This will only work on Toshiba devices supporting this feature.
Note: The logs are quite large - typically 100's of MB. This command can take several minutes to complete.
A progress runner is included when data is written to file and a page count is included in the stdout dump.
OPTIONS
-------
-o <FILE>::
--output-file=<FILE>::
Output binary file. Defaults to text-formatted dump to stdout
-p::
--prev-log::
Use previous log contents. Defaults to the current log contents.
EXAMPLES
--------
* Get the current log from the device and dump it to stdout:
+
------------
# nvme toshiba internal-log /dev/nvme0
------------
+
* Get the previous log from the device and save to a binary file:
+
------------
# nvme toshiba internal-log /dev/nvme0 --output-file=log.bin --prev-log
------------
NVME
----
Part of the nvme-user suite
|
