NVME_GET_LOG_ZNS_CHANGED_ZONES(2)

💖 nvme_get_log_zns_changed_zones(2) 💖

okay bestie, welcome to the libnvme API manual page for nvme_get_log_zns_changed_zones — yes that name is a whole mouthful, no we are not changing it, it's iconic actually 🫶

---

✨ NAME ✨

nvme_get_log_zns_changed_zones — Retrieve list of zones that have changed 💅

---

🌸 SYNOPSIS 🌸

int nvme_get_log_zns_changed_zones (int fd , __u32 nsid , bool rae ,
       struct nvme_zns_changed_zone_log *log );

like. five things. four of them go in. one int comes out. that's the whole deal bestie ✨

---

🎀 ARGUMENTS 🎀

• fd — File descriptor of nvme device 🔥 this is your ticket in, your little handle on the drive
• nsid — Namespace ID 🦋 which namespace we're talking about, pls don't guess
• rae — Retain asynchronous events 🫶 the "keep the events, bestie" switch
• log — User address to store the changed zone log 💾 it's giving "here's where you put the answer"

---

🦋 DESCRIPTION 🦋

so basically 🥺 this one grabs you the list of zones that have changed state due to an exceptional event.

like — something happened to those zones. an exceptional event happened. and this call is the one that goes "okay so who changed" and hands you back the receipts. no cap. 💀

---

💜 RETURN 💜

• The nvme command status if a response was received — peep enum nvme_status_field for the whole menu of what that status could be 👑
• -1 with errno set — that's the "nope, it went sideways" path 😭 and yeah, errno is doing the explaining for you

fr fr: if you get that -1, go read errno before you go read anything else. she's the main character here. 🌈

---

🌟 SEE ALSO 🌟

no see-also section on this one bestie, this page is a standalone girlie 💅

---

okay that's the whole page, you ate it, periodt 💖 this little love letter is from the libnvme API manual, dated July 2026 — go log some zones, you got this 🎀✨🦋