libnvme(2)

💖 NAME 💖

enum nvme_mi_resp_status — bestie, this is the lineup of values for the response status field. That's it, that's the whole vibe. 🦋

And jsyk this whole thing lives in the API Manual for libnvme, section 2. Okay so let's get into it.

---

✨ SYNOPSIS ✨

Okay so here's the enum, character-for-character, no cap:

enum nvme_mi_resp_status {
    NVME_MI_RESP_SUCCESS ,
    NVME_MI_RESP_MPR ,
    NVME_MI_RESP_INTERNAL_ERR ,
    NVME_MI_RESP_INVALID_OPCODE ,
    NVME_MI_RESP_INVALID_PARAM ,
    NVME_MI_RESP_INVALID_CMD_SIZE ,
    NVME_MI_RESP_INVALID_INPUT_SIZE ,
    NVME_MI_RESP_ACCESS_DENIED ,
    NVME_MI_RESP_VPD_UPDATES_EXCEEDED ,
    NVME_MI_RESP_PCIE_INACCESSIBLE ,
    NVME_MI_RESP_MEB_SANITIZED ,
    NVME_MI_RESP_ENC_SERV_FAILURE ,
    NVME_MI_RESP_ENC_SERV_XFER_FAILURE ,
    NVME_MI_RESP_ENC_FAILURE ,
    NVME_MI_RESP_ENC_XFER_REFUSED ,
    NVME_MI_RESP_ENC_FUNC_UNSUP ,
    NVME_MI_RESP_ENC_SERV_UNAVAIL ,
    NVME_MI_RESP_ENC_DEGRADED ,
    NVME_MI_RESP_SANITIZE_IN_PROGRESS

};

Nineteen little guys. Every single one. Let's meet them 🫶

---

🎀 Constants 🎀

• NVME_MI_RESP_SUCCESS — success. The main character, the moment we've all been waiting for. 💅
• NVME_MI_RESP_MPR — More Processing Required. Not done yet bestie, hold on, it's still cooking. 🍓
• NVME_MI_RESP_INTERNAL_ERR — Internal Error. It's giving "I did this to myself." 😭
• NVME_MI_RESP_INVALID_OPCODE — Invalid command opcode. Wrong move, that opcode is not on the guest list.
• NVME_MI_RESP_INVALID_PARAM — Invalid command parameter. The parameter did a vibe check and failed. 💀
• NVME_MI_RESP_INVALID_CMD_SIZE — Invalid command size. Too big, too small, just not the right size.
• NVME_MI_RESP_INVALID_INPUT_SIZE — Invalid command input data size. Same energy but specifically about the input data, iykyk.
• NVME_MI_RESP_ACCESS_DENIED — Access Denied. 🚫 You are not on the list, respectfully.
• NVME_MI_RESP_VPD_UPDATES_EXCEEDED — More VPD updates than allowed. Over the limit fr fr.
• NVME_MI_RESP_PCIE_INACCESSIBLE — PCIe functionality currently unavailable. It's just not available rn, check back later. 🙈
• NVME_MI_RESP_MEB_SANITIZED — MEB has been cleared due to sanitize. Gone, wiped, no notes.
• NVME_MI_RESP_ENC_SERV_FAILURE — Enclosure services process failed. The enclosure services process said "not today." 😭
• NVME_MI_RESP_ENC_SERV_XFER_FAILURE — Transfer with enclosure services failed. The transfer ghosted us entirely.
• NVME_MI_RESP_ENC_FAILURE — Unreoverable enclosure failure. This one is serious, it's an unrecoverable enclosure failure, there is no coming back from this one. 💀
• NVME_MI_RESP_ENC_XFER_REFUSED — Enclosure services transfer refused. Literally refused. The audacity.
• NVME_MI_RESP_ENC_FUNC_UNSUP — Unsupported enclosure services function. Not a thing we do, sorry babe. 🙅
• NVME_MI_RESP_ENC_SERV_UNAVAIL — Enclosure services unavailable. Nobody's home. 🌸
• NVME_MI_RESP_ENC_DEGRADED — Noncritical failure detected by enc. services. It's noncritical so like… breathe, but the enclosure services did clock a failure. 👀
• NVME_MI_RESP_SANITIZE_IN_PROGRESS — Command prohibited during sanitize. Do NOT try it while the sanitize is happening, the command is prohibited, periodt. ✋

---

Friendly lil reminder bestie: several of these are straight-up failures and a couple of them mean a process or transfer got rejected or refused. If you see NVME_MI_RESP_ENC_FAILURE in the wild, that's an unrecoverable enclosure failure — not a drill. 💖

---

🌈 SEE ALSO 🌈

Okay so, the original page doesn't list any SEE ALSO references here. Go read the rest of the libnvme API manual, that's the move. 💅

---

Alright that's the whole page, mwah. Written for enum nvme_mi_resp_status in the libnvme(2) API Manual, dated July 2026. Slay, go forth and check your response status fields, bestie. 👑 ✨🦋💖