nvme_verify(2)

✨ nvme_verify — the libnvme API manual, but make it cute 💅

okay bestie, welcome to the nvme_verify page of the libnvme API manual 🎀 yes that's a section 2 situation, we're in the syscall/library zone, come on in 🦋

---

👑 NAME

nvme_verify — sends an nvme verify command ✨ like, that's the whole job. she verifies. that's her.

---

🌸 SYNOPSIS

int nvme_verify (struct nvme_io_args *args );

---

🫶 ARGUMENTS

• args — a struct nvme_io_args argument structure 💖 (yes bestie, it's the arg struct, she's carrying the whole vibe)

---

💫 DESCRIPTION

okay so the Verify command does a vibe check on your stored information 🔍 — she verifies the integrity of it by reading data and metadata, if applicable, for the LBAs indicated 🌈

and here's the gag, the iconic part: she does all of that without transferring any data or metadata to the host 💅 no cap. she looks. she checks. she says nothing back to you. main character energy honestly 👑

---

🔥 RETURN

so what do you get back? 🌸

• the nvme command status if a response was received — peep enum nvme_status_field for the deets 🫡
• or -1 with errno set, otherwise 😭

ngl bestie, if you see that -1 just go read your errno, she's trying to tell you something fr fr 💀

---

🩷 SEE ALSO

(the original page doesn't list any SEE ALSO refs, so we're just gonna ✨ skip ✨ — but shoutout to enum nvme_status_field, we see you 🌟)

---

aaaaand that's the whole page, no notes 🎀 this was written in July 2026 (the date on the footer bestie, iykyk 📅) and it belongs to the libnvme API manual — nvme_verify, section 2, periodt 💖 byeee, go verify something 🦋✨🧚‍♀️