nvme_mi_adm...ia_unit_stat(2)

✨ nvme_mi_admin_get_log_media_unit_stat(2) ✨

okay bestie, welcome to the libnvme API manual 💖 you're about to read up on nvme_mi_admin_get_log_media_unit_stat(2) and honestly? it's giving "grab the receipts on your storage media units." let's get into it 🫶

---

🌸 NAME 🌸

nvme_mi_admin_get_log_media_unit_stat — Retrieve Media Unit Status 💅

like... go get the status. of the media units. that's the whole job. slay.

---

🎀 SYNOPSIS 🎀

int nvme_mi_admin_get_log_media_unit_stat (nvme_mi_ctrl_t ctrl , __u16
domid , struct nvme_media_unit_stat_log *mus );

yes it wraps like that, she's a long one, we don't judge 💜 (we DO copy her exactly tho, character for character, no cap)

---

🦋 ARGUMENTS 🦋

• ctrl — the Controller to query 👑 this is your main character, the thing you're asking questions about
• domid — Domain Identifier selection, if supported 🌈 (that "if supported" is doing a lot of work here, don't forget it, bestie)
• mus — User address to store the Media Unit statistics log 🍓 like, hand her an address and she'll drop the stats there

---

🌟 RETURN 🌟

so here's what comes back, periodt:

• the nvme command status, if a response was received — peep enum nvme_status_field for the full tea ☕
• -1 with errno set, otherwise 😭

fr fr, that's either a status code or a -1 + errno. no in-between, no vibes-based guessing ✨

---

💌 one lil sign-off 💌

this page came to you from the libnvme API manual, dated July 2026 — and it lives at nvme_mi_adm...ia_unit_stat(2), which, ik, the name got a lil truncated in the header, it's fine, she's iconic regardless 👑 read it, love it, go query your controller 💖✨

🦋 mwah, bye bestie 🦋