nvme_mi_adm...urance_group(2)

💖 nvme_mi_admin_get_log_endurance_group — from the nvme_mi_adm...urance_group(2) page in the libnvme API manual

okay bestie, gather round, because we're talking about getting the Endurance Group log and honestly?? it's giving detective work. 🔍✨

---

🌸 NAME 🌸

nvme_mi_admin_get_log_endurance_group — Get Endurance Group log

---

🎀 SYNOPSIS 🎀

int nvme_mi_admin_get_log_endurance_group (nvme_mi_ctrl_t ctrl , __u16
endgid , struct nvme_endurance_group_log *log );

---

✨ ARGUMENTS ✨

• ctrl — the Controller you're querying. your main character, the one we interrogate 💅
• endgid — the Starting group identifier to return in the list. like, where do we start scrolling, bestie
• log — User address to store the endurance log. this is the lil container where the tea gets poured 🫖

---

🦋 DESCRIPTION 🦋

so this log page? it tells you if an Endurance Group Event has occurred for a particular Endurance Group. that's it. that's the vibe check.

and if an Endurance Group Event has occurred, then the details of that particular event are included in the Endurance Group Information log page for that Endurance Group. no cap — the specifics live over there.

also!! an asynchronous event gets generated when an entry for an Endurance Group is newly added to this log page. like, the log page literally gets a notif. iconic behaviour, honestly. 🔔

---

💀 RETURN 💀

• The nvme command status if a response was received (see enum nvme_status_field)
• or -1 with errno set otherwise.

so basically: it either tells you how it went, or it hits you with the -1 and makes you go read errno. 😭

---

remembe bestie: check errno when you see that -1. she's not being dramatic, she's being informative. 🎀

---

and that's the whole page fr fr — shoutout to the libnvme API manual, dated July 2026. slay, go log some endurance groups. 💅👑💖