NVME_IDENTIFY_ACTIVE_NS_LIST(2)

✨ NAME ✨

nvme_identify_active_ns_list — bestie, this one retrieves active namespaces id list 💖

okay so real quick, we're deep in the libnvme API manual today, and this little function is your girl for finding out which namespaces are actually, you know, alive on your NVMe device. no cap. 🦋

---

🌸 SYNOPSIS 🌸

int nvme_identify_active_ns_list (int fd , __u32 nsid , struct
       nvme_ns_list *list );

like, that's the whole vibe. three args, one int coming back at you. iconic. 💅

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of your nvme device. your little handle to the hardware, your main character connection 🔥
• nsid — "return namespaces greater than this identifier" — so this is your starting point, your cutoff, your "everything above this line bestie" ✨
• list — user space destination address to transfer the data. i.e. where you want the goodies dropped off 💖

---

🧚 DESCRIPTION 🧚

so here's the tea. ☕

A list of 1024 namespace IDs gets returned to the host, and it contains NSIDs in increasing order that are greater than the value you specified in the Namespace Identifier (nsid) field of the command. so like, strictly greater-than energy, not equal, not less. slay. 👑

and if you wanna know exactly what that returned structure is shaped like? go peek at struct nvme_ns_list, that's where the definition lives. iykyk. 🫶

---

💀 RETURN 💀

What you get back is the nvme command status if a response was received (heads up, see enum nvme_status_field for the deets on that btw 🌈) — or -1 with errno set otherwise. so if it's -1, something went sideways and errno is gonna tell you what. 🙈

lowkey always check the return value, bestie. -1 is not a vibe, it's a warning. 😭

---

and that's the whole page fr fr — every arg, every number, every return path, nothing skipped, we ate and left no crumbs 🍓

that's a wrap on this one babes, brought to you by the libnvme API manual, July 2026 edition — go identify some namespaces and stay hydrated 💜✨