LLAPI_LMV_GET_UUIDS(3)

πŸ“¦ version 2.17.58, in ubuntu stonking

πŸ’– llapi_lmv_get_uuids(3) β€” the Lustre girlies' guide to getting device uuids πŸ’–

okay so bestie, you're holding the manual page for llapi_lmv_get_uuids(3), and honestly? it's a short one but it's lowkey iconic. two little functions, both about pulling device uuids out of a mounted Lustre thing. let's get into it πŸ¦‹


✨ NAME ✨

llapi_lmv_get_uuids, llapi_lov_get_uuids β€” get device uuids. that's it, that's the whole vibe. πŸ’…


🌸 SYNOPSIS 🌸

#include <lustre/lustreapi.h>

int llapi_lmv_get_uuids(int fd, struct obd_uuid *uuidp, int *mdt_count);
int llapi_lov_get_uuids(int fd, struct obd_uuid *uuidp, int *ost_count);
yes the original page really does have trailing quote marks at the end of those two lines, and no, we don't know why either. the way that… 🫢 anyway, copy the signatures as written above and you're golden.

πŸ’œ DESCRIPTION πŸ’œ

so llapi_lmv_get_uuids() and llapi_lov_get_uuids()? their whole job is getting the uuids for their respective device type. one's the LMV situation, one's the LOV situation. they pull uuids, that's the assignment, and they ate. πŸ”₯

now the deets on the arguments, bestie, because this part matters:

  • fd β€” this is the file descriptor for the mount point. not just any random fd, okay? it's giving "I need to know which mount you're talking about." 🌈
  • uuidp β€” this is a preallocated array of obd_uuid that's gonna hold the uuids. preallocated!! you bring the space, the function fills it. it's a potluck and you're the one bringing the dishware πŸ“
  • ost_count β€” after the call, this returns the count of uuids sitting in that uuidp array. literally the headcount for your uuid party πŸŽ€

⭐ RETURN VALUES ⭐

on success, you get the device uuids back, no cap. on failure? you get a negative errno value. so like, check for that negativity before you start celebrating. if your return value is being emo, something went wrong 😭


πŸ‘‘ AVAILABILITY πŸ‘‘

llapi_lmv_get_uuids() and llapi_lov_get_uuids() are part of the lustre(7) user application interface library, and they've been in there since before release 2.17.0. so they're not new-new, they're seasoned. main character energy that's been main character energy for a while πŸ’–


πŸ¦‹ SEE ALSO πŸ¦‹


and that's the whole page, bestie, you're fully caught up 🫢 this was Lustre User API, dated 2025-06-05, and honestly? iconic of it. go get those uuids. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from