lsm_fs_ss_list(3)
π lsm_fs_ss_list(3) β the Libstoragemgmt C API Manual π
okay bestie, gather round, because we're about to get you a whole LIST of snapshots for a file system and it's gonna be so clean. this one lives in the Libstoragemgmt C API Manual and it's giving β¨organized chaosβ¨ in the best way. let's go π¦
β¨ NAME β¨
lsm_fs_ss_list β gets you a list of snapshots of a specified file system. that's it, that's the job, and it does it beautifully π
πΈ SYNOPSIS πΈ
int lsm_fs_ss_list (lsm_connect *conn, lsm_fs *fs, lsm_fs_ss **ss[],
uint32_t *ss_count, lsm_flag flags);
π ARGUMENTS π
connβ a valid connection. like, an actual real one. don't be out here passing nonsense, the vibes will NOT survive it πfsβ pointer oflsm_fsto check for snapshots. this is the file system we're snooping on, bestie, respectfully π«Άss[]β output pointer oflsm_fs_ssarray. and listen, this array is YOURS to clean up β it has to be manually freed bylsm_fs_ss_record_array_free. no cap, you gotta free it yourself or that memory just sits there like an unread group chat πss_countβ number of elements in the array. how many snapshots did we find? this tells you. iconic behavior tbh πflagsβ reserved for future use, must beLSM_CLIENT_FLAG_RSVD. it's not doing anything yet, it's just chilling in the corner waiting for its main character moment β
π¦ VERSION π¦
1.0
π DESCRIPTION π
Gets a list of file systems snapshots on this connection. so like, you hand it a connection, and it comes back with the whole snapshot situation for you. lowkey magical β¨
File system snapshot properties could be retrieved by these functions:
lsm_fs_ss_id_getlsm_fs_ss_name_getlsm_fs_ss_time_stamp_get
that's your little trio right there β id, name, time stamp. the way that they just hand you all the deets on each snapshot?? obsessed π
π CAPABILITY π
LSM_CAP_FS_SNAPSHOTS
π₯ RETURN π₯
Error code as enumerated by lsm_error_number. here's the whole roster, no gatekeeping:
LSM_ERR_OK- On success or searched value not found. yes bestie, "not found" still counts as okay here, that's just how it is π
LSM_ERR_INVALID_ARGUMENT- When any argument is
NULLor invalid flags or invalid search key. something came in wrong and we're calling it out π©
- When any argument is
LSM_ERR_NO_SUPPORT- Not supported. the hardware/backend said no and honestly? respect π
okay so quick reminder before you go: free thatss[]array withlsm_fs_ss_record_array_free. i'm not nagging, i'm caring π
and that's the whole page, bestie! this was Libstoragemgmt C API Manual, version 1.0, dated February 2026 β thanks for reading, you ate that, periodt πβ¨
π¦ 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