NVME_MI_ADMIN_GET_LOG_SANITIZE(2)

πŸ’– nvme_mi_admin_get_log_sanitize β€” Retrieve Sanitize Status πŸ’–

okay bestie, welcome to the libnvme API manual ✨ this one's literally nvme_mi_admin_get_log_sanitize(2) and it's about finding out how your sanitize sitch is going. no cap.


🌸 NAME 🌸

nvme_mi_admin_get_log_sanitize β€” Retrieve Sanitize Status 🧼


✨ SYNOPSIS ✨

int nvme_mi_admin_get_log_sanitize (nvme_mi_ctrl_t ctrl , bool rae ,
       struct nvme_sanitize_log_page *log );

like. that's the whole vibe. three args, one int back. iconic. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl β€” the Controller to query, aka the one you're asking "hey girl, how's the sanitize going?" πŸ‘‘
  • rae β€” Retain asynchronous events. yes queen, keep those events, don't let them ghost you 🫢
  • log β€” User address to store the sanitize log. so like, you gotta hand it somewhere to put the tea β˜•

πŸ¦‹ DESCRIPTION πŸ¦‹

The Sanitize Status log page reports sanitize operation time estimates and information about the most recent sanitize operation. that's the whole plot. it's giving receipts on your last sanitize and how long the current one thinks it's gonna take. πŸ•βœ¨


πŸ’€ RETURN πŸ’€

The nvme command status if a response was received (see enum nvme_status_field) β€” or -1 with errno set otherwise. so like, if it answers you get the status, and if it doesn't, it's -1 and errno is doing the talking. no in-between bestie 🫠

lowkey important: -1 always comes with errno set. check it. it's not optional, it's a whole lifestyle πŸ’…

🌈 SEE ALSO 🌈

nothing else listed here, so that's the whole friend group. just this one. main character energy only ✨


okay that's the page!! this was from the libnvme API manual, the page is nvme_mi_admin_get_log_sanitize(2), and the date on it is July 2026. ty for reading bestie, go sanitize something responsibly πŸ’–πŸŽ€πŸ¦‹ (also literally check errno, i'm begging) 🌸

πŸ“¦ where this page comes from