NVME_GET_LOG_ENDURANCE_GRP_EVT(2)

✨ nvme_get_log_endurance_grp_evt(2) ✨

okay bestie, so this one lives in the libnvme API manual, and the function we're hyping up today is nvme_get_log_endurance_grp_evt β€” say that five times fast, I dare you πŸ’€


πŸ’– NAME πŸ’–

nvme_get_log_endurance_grp_evt β€” go get that Endurance Group Event Aggregate πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int nvme_get_log_endurance_grp_evt (int fd , bool rae , __u32 offset ,
       __u32 len , void *log );

🌸 ARGUMENTS 🌸

  • fd β€” the file descriptor of the nvme device. like, your little handle to the drive itself bestie 🫢
  • rae β€” Retain asynchronous events. flip this and the events stay put instead of ghosting you
  • offset β€” where in the log page you wanna start reading from. offset to the start of the log page, periodt
  • len β€” how much space you've got allocated for the log page. the allocated length, no cap
  • log β€” the user address where the log page gets stored. hand it a buffer and it'll fill it up πŸ’…

πŸ”₯ RETURN πŸ”₯

If a response actually came back, you get the nvme command status β€” peek at enum nvme_status_field for the deets. If not? it's -1 with errno set. rude, but that's the deal 😭

ngl bestie, always check the return value. -1 is not the vibe you want to see at 3am.

and that's the whole page, you ate that πŸ’– stay iconic, keep your buffers big enough, and remember: this is the libnvme API manual, dated July 2026 β€” written for the girlies who read manpages for fun πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from