nvme_init_sanitize_nvm(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’– NAME πŸ’–

nvme_init_sanitize_nvm β€” initialize passthru command to start a sanitize operation ✨

okay so bestie, you're on the nvme_init_sanitize_nvm(9) page from the libnvme API manual, and this whole page is about setting up the passthru command so it can start a sanitize operation πŸ’…


✨ SYNOPSIS ✨

void nvme_init_sanitize_nvm (struct libnvme_passthru_cmd *cmd , enum
       nvme_sanitize_sanact sanact , bool ause , __u8 owpass , bool oipbp ,
       bool ndas , bool emvs , bool preq , __u32 ovrpat );

πŸŽ€ ARGUMENTS πŸŽ€

  • cmd β€” the passthru command you're using 🫢
  • sanact β€” the sanitize action; see enum nvme_sanitize_sanact πŸ‘‘
  • ause β€” set this to allow unrestricted sanitize exit πŸ¦‹
  • owpass β€” overwrite pass count 🌸
  • oipbp β€” set to overwrite invert pattern between passes πŸ”₯
  • ndas β€” set to not deallocate blocks after sanitizing πŸ’€
  • emvs β€” set to enter media verification state ⭐
  • preq β€” set to require the sanitize operation to purge user data, as defined by IEEE Std 2883, or fail 😭
  • ovrpat β€” overwrite pattern πŸ“

πŸ¦‹ DESCRIPTION πŸ¦‹

Think of it as the setup step: it initializes the passthru command buffer for the Sanitize NVM command, periodt πŸ’…

no cap, preq is the one carrying the IEEE Std 2883 requirement and the "or fail" energy β€” handle with care πŸ™ˆ

that's the tea from the libnvme API manual, October 2026 edition, page nvme_init_sanitize_nvm(9) β€” periodt πŸ’–βœ¨

πŸ“¦ where this page comes from