lsm_fs_ss_list(3)

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

πŸ’– 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 of lsm_fs to check for snapshots. this is the file system we're snooping on, bestie, respectfully 🫢
  • ss[] β€” output pointer of lsm_fs_ss array. and listen, this array is YOURS to clean up β€” it has to be manually freed by lsm_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 be LSM_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_get
  • lsm_fs_ss_name_get
  • lsm_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 NULL or invalid flags or invalid search key. something came in wrong and we're calling it out 🚩
  • LSM_ERR_NO_SUPPORT
    • Not supported. the hardware/backend said no and honestly? respect πŸ’€

okay so quick reminder before you go: free that ss[] array with lsm_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