lsm_volume_list(3)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

✨ lsm_volume_list β€” the Libstoragemgmt C API Manual glow-up ✨

okay bestie, welcome to lsm_volume_list from the Libstoragemgmt C API Manual πŸ’– this is the one that hands you a whole list of volumes on your connection, and honestly? iconic behaviour.


🌸 NAME 🌸

lsm_volume_list β€” gets a list of volumes on this connection. that's it, that's the vibe. πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

int lsm_volume_list (lsm_connect *conn, const char *search_key, const
char *search_value, lsm_volume **volumes[], uint32_t *count, lsm_flag
flags);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • conn β€” a valid lsm_connect pointer. like, an actually valid one. don't be playing games with me here πŸ™ˆ
  • search_key β€” your search key, and it's NULL for all of them. the valid search keys are: "id", "system_id" and "pool_id". that's the whole list, no extras, no secret menu πŸ’…
  • search_value β€” the search value. the matching half of the little search duo 🫢
  • volumes[] β€” output pointer of the lsm_volume array. lowkey important: it should be manually freed by lsm_volume_record_array_free. yes, manually. you, personally. do not ghost it, bestie, that's a leak 😭
  • count β€” output pointer of uint32_t. number of volumes. how many you got ✨
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. no freelancing on this one 🚫

⭐ VERSION ⭐

1.0


πŸ’œ DESCRIPTION πŸ’œ

Gets a list of volumes on this connection. the way that this function just… gathers up all your volumes, no cap 🌈

Volume properties could be retrieved by these functions:

  • lsm_volume_id_get
  • lsm_volume_name_get
  • lsm_volume_system_id_get
  • lsm_volume_vpd83_get
  • lsm_volume_number_of_blocks_get
  • lsm_volume_block_size_get
  • lsm_volume_admin_state_get
  • lsm_volume_pool_id_get

all eight of them, collected, matching set, main character energy πŸ‘‘


🧚 CAPABILITY 🧚

LSM_CAP_VOLUMES


πŸ”₯ RETURN πŸ”₯

Error code as enumerated by lsm_error_number. here's the rundown:

  • LSM_ERR_OK β€” on success or searched value not found. yes, "not found" still counts as okay here, that's just how she is πŸ’–
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL or invalid flags or invalid search key. basically if you handed her nonsense, she's telling you 🫠
  • LSM_ERR_NO_SUPPORT β€” not supported. she simply cannot, bestie πŸ’€

lowkey reminder: that volumes[] array is yours to free with lsm_volume_record_array_free. fr fr, don't skip it. 🌸

that's the whole page, bestie β€” lsm_volume_list(3) from the Libstoragemgmt C API Manual, version 1.0, dated February 2026. slay, go forth, and free your arrays πŸ’…βœ¨

πŸ“¦ where this page comes from