summaryrefslogtreecommitdiffstats
path: root/Documentation/nvme-wdc-purge-monitor.txt
blob: 313c8db1920c91af71a6bed1464ab48389c8ffed (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
nvme-wdc-purge-monitor(1)
=========================

NAME
----
nvme-wdc-purge-monitor - Send NVMe WDC Purge-Monitor Vendor Unique Command, return result

SYNOPSIS
--------
[verse]
'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 :-

[cols="2*", options="header"]
|===
|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.