NVMe sanitize
NVMe Sanitize starts a controller-managed sanitization operation using a supported Block Erase, Overwrite or Crypto Erase action.
The cited Base Specification 2.0e describes background processing: command completion is not operation completion. Inspect controller capabilities and the Sanitize Status log. Interpret the status field, not only progress: SPROG is FFFFh whenever the operation is not in progress, including states that do not establish success.
Unlike Format NVM, Sanitize is a separate background operation. Its user-data scope includes overprovisioned storage and it resumes after power interruption; this is not a claim that every device byte is user data.
Global Data Erased is separate from operation completion. A rejected Sanitize command can leave the previous result in the log; correlate the command outcome and log. The companion analysis supplies synthetic status examples and a tested, revision-scoped interpreter. Do not apply the 2.0e layout blindly to newer revisions.
Relations
- related
- NVMe, Secure erase, Data sanitization, Cryptographic erase, Sanitization verification, Sanitization validation, NVMe Format NVM, LUKS header backup
Advantages
- Provides a dedicated status log for the sanitization operation. [1]
Limitations
- Supported actions vary; verify capability and completion before accepting the result. [1]