| 1 |
.TH "nvme_get_log_smart" 9 "nvme_get_log_smart" "November 2025" "libnvme API manual" LINUX |
| 2 |
.SH NAME |
| 3 |
nvme_get_log_smart \- Retrieve nvme smart log |
| 4 |
.SH SYNOPSIS |
| 5 |
.B "int" nvme_get_log_smart |
| 6 |
.BI "(int fd " "," |
| 7 |
.BI "__u32 nsid " "," |
| 8 |
.BI "bool rae " "," |
| 9 |
.BI "struct nvme_smart_log *smart_log " ");" |
| 10 |
.SH ARGUMENTS |
| 11 |
.IP "fd" 12 |
| 12 |
File descriptor of nvme device |
| 13 |
.IP "nsid" 12 |
| 14 |
Optional namespace identifier |
| 15 |
.IP "rae" 12 |
| 16 |
Retain asynchronous events |
| 17 |
.IP "smart_log" 12 |
| 18 |
User address to store the smart log |
| 19 |
.SH "DESCRIPTION" |
| 20 |
This log page provides SMART and general health information. The information |
| 21 |
provided is over the life of the controller and is retained across power |
| 22 |
cycles. To request the controller log page, the namespace identifier |
| 23 |
specified is FFFFFFFFh. The controller may also support requesting the log |
| 24 |
page on a per namespace basis, as indicated by bit 0 of the LPA field in the |
| 25 |
Identify Controller data structure. |
| 26 |
.SH "RETURN" |
| 27 |
The nvme command status if a response was received (see |
| 28 |
\fIenum nvme_status_field\fP) or -1 with errno set otherwise. |