| 1 |
.TH "libnvme" 9 "struct nvme_st_result" "November 2025" "API Manual" LINUX |
| 2 |
.SH NAME |
| 3 |
struct nvme_st_result \- Self-test Result |
| 4 |
.SH SYNOPSIS |
| 5 |
struct nvme_st_result { |
| 6 |
.br |
| 7 |
.BI " __u8 dsts;" |
| 8 |
.br |
| 9 |
.BI " __u8 seg;" |
| 10 |
.br |
| 11 |
.BI " __u8 vdi;" |
| 12 |
.br |
| 13 |
.BI " __u8 rsvd;" |
| 14 |
.br |
| 15 |
.BI " __le64 poh;" |
| 16 |
.br |
| 17 |
.BI " __le32 nsid;" |
| 18 |
.br |
| 19 |
.BI " __le64 flba;" |
| 20 |
.br |
| 21 |
.BI " __u8 sct;" |
| 22 |
.br |
| 23 |
.BI " __u8 sc;" |
| 24 |
.br |
| 25 |
.BI " __u8 vs[2];" |
| 26 |
.br |
| 27 |
.BI " |
| 28 |
}; |
| 29 |
.br |
| 30 |
|
| 31 |
.SH Members |
| 32 |
.IP "dsts" 12 |
| 33 |
Device Self-test Status: Indicates the device self-test code and the |
| 34 |
status of the operation (see \fIenum nvme_status_result\fP and \fIenum nvme_st_code\fP). |
| 35 |
.IP "seg" 12 |
| 36 |
Segment Number: Iindicates the segment number where the first self-test |
| 37 |
failure occurred. If Device Self-test Status (\fIdsts\fP) is not set to |
| 38 |
#NVME_ST_RESULT_KNOWN_SEG_FAIL, then this field should be ignored. |
| 39 |
.IP "vdi" 12 |
| 40 |
Valid Diagnostic Information: Indicates the diagnostic failure |
| 41 |
information that is reported. See \fIenum nvme_st_valid_diag_info\fP. |
| 42 |
.IP "rsvd" 12 |
| 43 |
Reserved |
| 44 |
.IP "poh" 12 |
| 45 |
Power On Hours (POH): Indicates the number of power-on hours at the |
| 46 |
time the device self-test operation was completed or aborted. This |
| 47 |
does not include time that the controller was powered and in a low |
| 48 |
power state condition. |
| 49 |
.IP "nsid" 12 |
| 50 |
Namespace Identifier (NSID): Indicates the namespace that the Failing |
| 51 |
LBA occurred on. Valid only when the NSID Valid bit |
| 52 |
(#NVME_ST_VALID_DIAG_INFO_NSID) is set in the Valid Diagnostic |
| 53 |
Information (\fIvdi\fP) field. |
| 54 |
.IP "flba" 12 |
| 55 |
Failing LBA: indicates the LBA of the logical block that caused the |
| 56 |
test to fail. If the device encountered more than one failed logical |
| 57 |
block during the test, then this field only indicates one of those |
| 58 |
failed logical blocks. Valid only when the NSID Valid bit |
| 59 |
(#NVME_ST_VALID_DIAG_INFO_FLBA) is set in the Valid Diagnostic |
| 60 |
Information (\fIvdi\fP) field. |
| 61 |
.IP "sct" 12 |
| 62 |
Status Code Type: This field may contain additional information related |
| 63 |
to errors or conditions. Bits 2:0 may contain additional information |
| 64 |
relating to errors or conditions that occurred during the device |
| 65 |
self-test operation represented in the same format used in the Status |
| 66 |
Code Type field of the completion queue entry (refer to \fIenum nvme_status_field\fP). |
| 67 |
Valid only when the NSID Valid bit (#NVME_ST_VALID_DIAG_INFO_SCT) is |
| 68 |
set in the Valid Diagnostic Information (\fIvdi\fP) field. |
| 69 |
.IP "sc" 12 |
| 70 |
Status Code: This field may contain additional information relating |
| 71 |
to errors or conditions that occurred during the device self-test |
| 72 |
operation represented in the same format used in the Status Code field |
| 73 |
of the completion queue entry. Valid only when the SCT Valid bit |
| 74 |
(#NVME_ST_VALID_DIAG_INFO_SC) is set in the Valid Diagnostic |
| 75 |
Information (\fIvdi\fP) field. |
| 76 |
.IP "vs" 12 |
| 77 |
Vendor Specific. |