libnvme(9)

💅 NAME

okay so bestie, welcome to libnvme(9) — the API Manual, and today's main character is enum nvme_cmd_format_ses 🎀 which is literally the Format NVM - Secure Erase Settings situation. yes. we're getting into erase vibes. buckle up 🦋

---

✨ SYNOPSIS

here's the whole thing, exactly as it lives, no cap:

enum nvme_cmd_format_ses {
    NVME_FORMAT_SES_NONE ,
    NVME_FORMAT_SES_USER_DATA_ERASE ,
    NVME_FORMAT_SES_CRYPTO_ERASE

};

that's it. that's the enum. iconic. 👑

---

🎀 Constants

okay so these are the three constants and let me tell you each one has a whole personality 🌸

• NVME_FORMAT_SES_NONE — No secure erase operation requested. literally nothing happening, we're just chilling 💅
• NVME_FORMAT_SES_USER_DATA_ERASE — User Data Erase, and the tea is: All user data shall be erased, and ngl the contents of the user data after the erase is indeterminate 😭 like, e.g. the user data may be zero filled, one filled, etc. — nobody knows, it's giving mystery ✨

and a little plot twist for you: if a User Data Erase is requested and all affected user data is encrypted, then the controller is allowed to use a cryptographic erase to perform the requested User Data Erase 🫶 slay, efficient.

• NVME_FORMAT_SES_CRYPTO_ERASE — Cryptographic Erase: All user data shall be erased cryptographically. and the way that it's accomplished? by deleting the encryption key 🔥 like, the key is gone, the data is gone, bye. no notes. 💀

---

🐝 quick vibe check reminder: the User Data Erase one does not promise you nice clean zeros afterward — "indeterminate" is doing a lot of heavy lifting there, so don't come crying when the contents look weird 🙈

---

so that's the whole page, bestie — every constant, every caveat, every last drop of erase lore 💖

and before you go: this absolute gem came from enum nvme_cmd_format_ses in the libnvme(9) API Manual, dated October 2026 🔥 bookmark it, screenshot it, send it to the group chat. mwah 💋 🦋 ⭐