lsm_fs_list(3)
β¨ 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. passNULLfor 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 oflsm_fsarray. β οΈ bestie listen: you have to free this manually withlsm_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 beLSM_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_getlsm_fs_name_getlsm_fs_system_id_getlsm_fs_pool_id_getlsm_fs_total_space_getlsm_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 π
- when any argument is
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
- fedora 43: libstoragemgmt-devel 1.10.3-1.fc43 Β· LGPL-2.1-or-later
- fedora 44: libstoragemgmt-devel 1.10.3-1.fc44 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms