nvme_identify_ns(2)

💅 nvme_identify_ns — bestie edition

okay so like. you're in the libnvme API manual, section 2, and the star of the show is nvme_identify_ns. she's the one who goes and gets you the identify namespace data. no cap. 🦋

---

✨ NAME ✨

nvme_identify_ns — retrieves nvme identify namespace

literally her whole job. she retrieves the nvme identify namespace. that's it, that's the gig. 💖

---

🌸 SYNOPSIS 🌸

int nvme_identify_ns (int fd , __u32 nsid , struct nvme_id_ns *ns );

look at her. three little args and she's out. iconic behavior honestly.

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of the nvme device. that's your way in, bestie, the little handle that says "yeah i know this drive".
• nsid — the namespace to identify. which one are we snooping on? this tells her.
• ns — the user space destination address to transfer the data. basically the bucket you're holding out so she can drop the data in. 🫶

---

👑 DESCRIPTION 👑

so here's the tea. if the Namespace Identifier (NSID) field specifies an active NSID, then the Identify Namespace data structure gets returned to the host for that specified namespace. so like, you point at a live namespace, you get its whole little identity card back. 💳✨

and here's the bonus round: if the controller supports the Namespace Management capability and the NSID field is set to NVME_NSID_ALL, then the controller returns an Identify Namespace data structure that specifies capabilities that are common across namespaces for this controller. so instead of one namespace's vibes, you get the shared group-chat-wide vibes. 🌈 periodt.

heads up bestie — wanna know what's actually inside the thing you get back? go look at struct nvme_id_ns for the details on the structure returned. that's where the full anatomy lives. 🔍

---

🔥 RETURN 🔥

she returns the nvme command status if a response was received — check enum nvme_status_field for the deets on that. and if no response came back at all? you get -1 and errno is set. 😭 not her fault, that's just how the API do.

---

okay and one last thing before you go 🎀 — this whole page comes to you courtesy of the libnvme API manual, and it's the July 2026 edition, filed under nvme_identify_ns in manpage section (2). go forth and identify those namespaces, bestie, you're gonna slay 💅✨🌸