NVME_IDENTIFY_NS_GRANULARITY(2)

✨ NAME ✨

nvme_identify_ns_granularity — bestie, this one retrieves namespace granularity identification 💖 it's giving "tell me how chunky your namespaces are" energy, fr fr

(this page lives in the libnvme API manual, section 2, iykyk 🦋)

---

🌸 SYNOPSIS 🌸

int nvme_identify_ns_granularity (int fd , struct
       nvme_id_ns_granularity_list *gr_list );

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of the nvme device, aka your little backstage pass to the controller 👑
• gr_list — user space destination address to transfer the data 🫶 that's where the goods land, no cap

---

💅 DESCRIPTION 💅

Okay so, the way that this works: if the controller supports reporting of Namespace Granularity, then a Namespace Granularity List gets returned to the host for up to sixteen namespace granularity descriptors. sixteen!! a whole sweet sixteen of them 🎂✨

See struct nvme_id_ns_granularity_list for the definition of the returned structure — that's where all the lore lives, go read it 💜

---

🔥 RETURN 🔥

It gives you the nvme command status if a response was received (peep enum nvme_status_field for that whole situation) — or -1 with errno set otherwise 😭 so always check, bestie, always.

no response = -1 + errno. that's the vibe check. don't ignore it 💀

---

that's the whole page, you ate it, periodt 🍓🧚

sign-off szn 💌 this came from the libnvme API manual, dated July 2026 — mwah, go granularity-identify something iconic ✨