libnvme(2)
π NAME π
okay bestie, gather round, because this one is literally the enum nvme_ae_info_css_nvm β aka Asynchronous Event Information - I/O Command Specific Status β¨
that's it. that's the whole vibe. it's giving "your drive has tea to spill about what just happened" π«
It lives in the libnvme manual, section 2 (that's the API Manual, for all my syscall girlies π )
πΈ SYNOPSIS πΈ
enum nvme_ae_info_css_nvm {
NVME_AER_CSS_NVM_RESERVATION ,
NVME_AER_CSS_NVM_SANITIZE_COMPLETED ,
NVME_AER_CSS_NVM_UNEXPECTED_SANITIZE_DEALLOC
};
no cap, that's the whole thing. three constants, zero drama π
π¦ Constants π¦
okay so these are the three moods your NVMe drive can be in when it fires off an I/O Command Specific Status asynchronous event. let's do a vibe check on each one π
NVME_AER_CSS_NVM_RESERVATIONβ Reservation Log Page Available. like, the reservation log page has arrived, bestie, it's here, it's serving πNVME_AER_CSS_NVM_SANITIZE_COMPLETEDβ Sanitize Operation Completed. the sanitize finished. clean girl aesthetic achieved β¨π§ΌNVME_AER_CSS_NVM_UNEXPECTED_SANITIZE_DEALLOCβ Sanitize Operation Completed With Unexpected Deallocation. sanitize finished BUT with an unexpected deallocation π not the plot twist we asked for, fr fr
no extra options, no flags, no environment variables, no exit statuses, no signals here β it's just three constants and honestly? iconic. minimalism ate π
and that's the whole page, bestie!! you now know enum nvme_ae_info_css_nvm better than 99% of people who touch NVMe on the daily π«Ά go forth and slay π
~ this was libnvme, section 2, from the API Manual, dated July 2026 ~ mwah π iykyk β
π¦ where this page comes from
- ubuntu stonking: libnvme-dev 1.16.2-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms