nvme_mi_adm...tive_ns_list(2)

💖 NAME 💖

nvme_mi_admin_identify_active_ns_list — bestie, this one does an Admin identify for an active namespace list ✨

(also hi, you're reading the libnvme API manual, welcome to the group chat 🫶)

---

✨ SYNOPSIS ✨

int nvme_mi_admin_identify_active_ns_list (nvme_mi_ctrl_t ctrl , __u32
nsid , struct nvme_ns_list *list );

okay so that's the whole vibe right there, no notes 💅

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller we're handing this identify command to. like, this is who's doing the work 💪
• nsid — the Namespace ID, and it's the one that says where the list starts. Not where it ends, where it starts, okay? 📍
• list — the list data we're populating. it's empty rn and we're about to fill it up, glow-up incoming 🌸

---

🌈 DESCRIPTION 🌈

So we're performing an Identify command, specifically for the active namespace list — and it starts with IDs that are greater than or equal to nsid 🦋

If you want the literal start of the list? Pass NVME_NSID_NONE for nsid. That's the move, bestie, do not skip that 📌

Now the part that's giving ✨trust issues✨ if you don't read it:

It will return an error if the length of the response data (from the controller) is not a full NVME_IDENTIFY_DATA_SIZE. But the slay here is that on success, list will be fully populated. no half-finished vibes, we don't do that 💀

See: struct nvme_ns_list 👀

---

👑 RETURN 👑

• The nvme command status if a response was received — go peek at enum nvme_status_field for the deets, iykyk
• or -1 with errno set, in literally every other case 🙈

---

💜 SEE ALSO 💜

girl. it's the same function, there's no other page here 😭 this one's a solo main character

---

okay that's the whole page, periodt 🎀 this was the libnvme API manual, dated July 2026 — mwah, go populate your namespace list, you're gonna ate 💅✨🦋