libnvme(9)

💅 NAME

enum nvme_status_result — the vibe check for your device self-test, aka the Result of the device self-test operation ✨

Bestie, this is the little enum that tells you how your device self-test went. Did it slay? Did it flop? Did it get unalived mid-test by a reset? All the answers live here 🎀

🌸 SYNOPSIS

enum nvme_status_result {
    NVME_ST_RESULT_NO_ERR ,
    NVME_ST_RESULT_ABORTED ,
    NVME_ST_RESULT_CLR ,
    NVME_ST_RESULT_NS_REMOVED ,
    NVME_ST_RESULT_ABORTED_FORMAT ,
    NVME_ST_RESULT_FATAL_ERR ,
    NVME_ST_RESULT_UNKNOWN_SEG_FAIL ,
    NVME_ST_RESULT_KNOWN_SEG_FAIL ,
    NVME_ST_RESULT_ABORTED_UNKNOWN ,
    NVME_ST_RESULT_ABORTED_SANITIZE ,
    NVME_ST_RESULT_NOT_USED ,
    NVME_ST_RESULT_SHIFT ,
    NVME_ST_RESULT_MASK

};

👑 CONSTANTS

Okay so here's the whole roster, no skips, fr fr:

• NVME_ST_RESULT_NO_ERR — the main character moment 💖 Operation completed without error. Literally the dream.
• NVME_ST_RESULT_ABORTED — Operation was aborted by a Device Self-test command. Not me getting canceled by my own command 😭
• NVME_ST_RESULT_CLR — Operation was aborted by a Controller Level Reset. The reset said "nope, we're done here" 💀
• NVME_ST_RESULT_NS_REMOVED — Operation was aborted due to a removal of a namespace from the namespace inventory. The namespace literally left the chat 🦋
• NVME_ST_RESULT_ABORTED_FORMAT — Operation was aborted due to the processing of a Format NVM command. Format came in and ate 🍓
• NVME_ST_RESULT_FATAL_ERR — A fatal error or unknown test error occurred while the controller was executing the device self-test operation and the operation did not complete. Yeah… that's a red flag bestie 🔥 not iconic at all.
• NVME_ST_RESULT_UNKNOWN_SEG_FAIL — Operation completed with a segment that failed and the segment that failed is not known. It flopped, but we don't know which part flopped 🙈 mysterious behavior honestly.
• NVME_ST_RESULT_KNOWN_SEG_FAIL — Operation completed with one or more failed segments and the first segment that failed is indicated in the Segment Number field. At least we got receipts ✨ go check the Segment Number field, iykyk.
• NVME_ST_RESULT_ABORTED_UNKNOWN — Operation was aborted for unknown reason. No explanation, just chaos 💀
• NVME_ST_RESULT_ABORTED_SANITIZE — Operation was aborted due to a sanitize operation. The sanitize said "excuse me, I'm busy" 🌈
• NVME_ST_RESULT_NOT_USED — Entry not used (does not contain a test result). Empty slot, nothing to see here, move along 🎀
• NVME_ST_RESULT_SHIFT — Device self-test result shift. The shift, the shifter, the one who shifts 🧚
• NVME_ST_RESULT_MASK — Mask to get the status result value from the struct nvme_st_result.dsts field. Use this to actually pull the value out of struct nvme_st_result.dsts — it's giving "unlock the lore" 🔑

Lowkey the whole point: NVME_ST_RESULT_SHIFT and NVME_ST_RESULT_MASK are your tools for extracting the status result value out of the struct nvme_st_result.dsts field. That's literally what NVME_ST_RESULT_MASK is for, periodt.

✨ That's the whole page bestie, every constant accounted for, not one skipped 💅 October 2026, API Manual for libnvme, section 9 — catch you in the next man page, mwah 🫶💜