nvme_get_log_sanitize(2)

💖 nvme_get_log_sanitize — it's a libnvme API manual bestie, section 2, and it's giving "Retrieve Sanitize Status" ✨

okay so picture this: you're deep in libnvme land, section 2 of the manual, and you need the tea on what your NVMe drive has been up to with sanitize operations. That's literally this whole page. Let's go. 🫶

---

🌸 NAME 🌸

nvme_get_log_sanitize — Retrieve Sanitize Status 👑

---

✨ SYNOPSIS ✨

int nvme_get_log_sanitize (int fd , bool rae , struct
       nvme_sanitize_log_page *log );

no cap, that's the whole signature. three little args and a dream. 💅

---

🎀 ARGUMENTS 🎀

• fd — File descriptor of nvme device. it's your lil backstage pass to the drive, iykyk 🔑
• rae — Retain asynchronous events. yes boo, keep those events, don't let 'em ghost you 🙈
• log — User address to store the sanitize log. this is where the gossip gets written down fr fr 🍓

---

🦋 DESCRIPTION 🦋

The Sanitize Status log page reports sanitize operation time estimates and information about the most recent sanitize operation.

so basically: how long is this sanitize thing gonna take, and what happened last time. the receipts, the timeline, the whole vibe check on your most recent sanitize operation. iconic behavior from a log page honestly. ⭐

---

🌈 RETURN 🌈

The nvme command status if a response was received (see enum nvme_status_field) or -1 with errno set otherwise.

so like — if the drive answered you, you get the nvme command status back (go peek at enum nvme_status_field for the deets). if it did NOT answer, you get -1 and errno gets set. that's your "it's not me, it's the errno" moment 😭

---

💜 SEE ALSO 💜

(ngl this page doesn't list any SEE ALSO refs, so we're just gonna vibe here together. go look at enum nvme_status_field if you're nosy though. 👀)

---

and that's the page bestie!! written up in July 2026, under the name nvme_get_log_sanitize, living in the <cyan>nvme_get_log_sanitize(2)</cyan> section of the libnvme API manual. mwah, go sanitize something safely, ily, byeeee 🧚💖✨