lsm_fs_list(3)

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

✨ lsm_fs_list ✨

okay bestie, welcome to lsm_fs_list(3) from the Libstoragemgmt C API Manual πŸ’– this one's a lil baddie that pulls up a whole list of file systems on your connection, and honestly? she ate.


🌸 NAME 🌸

lsm_fs_list β€” gets a list of file systems on this connection. that's it, that's the whole vibe πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int lsm_fs_list (lsm_connect *conn, const char *search_key, const char
*search_value, lsm_fs **fs[], uint32_t *fs_count, lsm_flag flags);

like. look at her. six args, zero chill πŸ¦‹


🫢 ARGUMENTS 🫢

  • conn β€” a valid connection. gotta have one, no connection no list, periodt.
  • search_key β€” the search key. pass NULL for all of them. the valid search keys are literally just: "id", "system_id" and "pool_id". that's the whole menu, don't get creative πŸ’€
  • search_value β€” the search value. yep. that's the value you're searching for. iconic pairing with the key above fr fr.
  • fs[] β€” output pointer of lsm_fs array. ⚠️ bestie listen: you have to free this manually with lsm_fs_record_array_free. she does not clean up after herself, that's on you.
  • fs_count β€” number of file systems. the count. the amount. the how-many. 🧚
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. it's giving "don't touch, not for you (yet)" πŸ™ˆ

πŸ’œ VERSION πŸ’œ

1.0


🌈 DESCRIPTION 🌈

gets a list of file systems on this connection. ok so here's the lore: a Network Attached Storage (NAS) storage array can expose a Filesystem to the host OS via IP network using NFS or CIFS protocol. the host OS treats it as a mount point or a folder containing files, depending on the client operating system. main character behaviour honestly πŸ‘‘

and if you wanna peek at the file system properties, these functions are the ones to hit up:

  • lsm_fs_id_get
  • lsm_fs_name_get
  • lsm_fs_system_id_get
  • lsm_fs_pool_id_get
  • lsm_fs_total_space_get
  • lsm_fs_free_space_get

⭐ CAPABILITY ⭐

LSM_CAP_FS


πŸ”₯ RETURN πŸ”₯

error code, as enumerated by lsm_error_number. the lineup:

  • LSM_ERR_OK
    • on success, or when the searched value is not found. yes really, "found nothing" still counts as okay. she's chill like that πŸ“
  • LSM_ERR_INVALID_ARGUMENT
    • when any argument is NULL, or invalid flags, or an invalid search key. basically when you didn't read the ARGUMENTS section 😭
  • LSM_ERR_NO_SUPPORT
    • not supported. rip. πŸ’€
no cap: check your return code. every single time. she will not warn you twice.

and that's the whole page bestie!! slay πŸ’…βœ¨ this was lsm_fs_list from the Libstoragemgmt C API Manual, source/version vibes dated February 2026, and it lives at lsm_fs_list(3). go forth and list some file systems, iykyk πŸ¦‹πŸŽ€πŸ’–

πŸ“¦ where this page comes from