libnvme(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvme(9) β€” API Manual, bestie edition ✨

Okay so this is a page from libnvme(9), aka the API Manual, and it's all about one lil enum that tells you how a drive can wipe your data. Yes, we're talking data removal mechanisms. It's giving "spring cleaning but make it firmware." Let's get into it πŸŽ€


NAME 🌸

enum tcg_l0_data_removal_mechanism β€” the supported data removal mechanisms, like the menu of ways your storage can say "new phone who dis" to your data 🫢


SYNOPSIS πŸ¦‹

Here's the whole enum, typed out exactly, no edits, no notes:

enum tcg_l0_data_removal_mechanism {
    TCG_L0_DATA_REMOVAL_OVERWRITE ,
    TCG_L0_DATA_REMOVAL_BLOCK_ERASE ,
    TCG_L0_DATA_REMOVAL_CRYPTO_ERASE ,
    TCG_L0_DATA_REMOVAL_VENDOR_ERASE

};

Literally that's it, that's the whole vibe check πŸ’…


Constants πŸ‘‘

TCG_L0_DATA_REMOVAL_OVERWRITE

Overwrite data erase ✨ like literally writing over the old stuff until it's gone. Classic, dependable, iconic.

TCG_L0_DATA_REMOVAL_BLOCK_ERASE

Block erase 🧚 blocks get erased, data goes bye-bye. Simple as that, no cap.

TCG_L0_DATA_REMOVAL_CRYPTO_ERASE

Cryptographic erase πŸ”₯ the crypto girlies know β€” erase via cryptography. Highkey my favorite, it's giving main character energy.

TCG_L0_DATA_REMOVAL_VENDOR_ERASE

Vendor specific erase 🌈 this one's the vendor's own special little method. Their house, their rules, iykyk.


Okay bestie real talk: those four constants are the entire list, and every single one has to stay exactly like that β€” TCG_L0_DATA_REMOVAL_OVERWRITE, TCG_L0_DATA_REMOVAL_BLOCK_ERASE, TCG_L0_DATA_REMOVAL_CRYPTO_ERASE, and TCG_L0_DATA_REMOVAL_VENDOR_ERASE. Don't be out here renaming them, I'm begging 😭

And that's the whole page, bestie! Mwah πŸ’– This was libnvme(9), the API Manual, dated October 2026, and it ate, no crumbs. Go forth and erase responsibly πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from