lsm_fs_ss_delete(3)

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

πŸ’… lsm_fs_ss_delete β€” from the Libstoragemgmt C API Manual

okay bestie, buckle up, we're deleting a snapshot today and honestly? iconic behavior. this one lives in section 3 of the Libstoragemgmt C API Manual, so it's a library function, not a command you type in your shell. iykyk 🫢


✨ NAME ✨

lsm_fs_ss_delete β€” Deletes a snapshot. yes. that's the whole job. she deletes, she slays, she leaves. πŸŽ€


🌸 SYNOPSIS 🌸

int lsm_fs_ss_delete (lsm_connect *conn, lsm_fs *fs, lsm_fs_ss *ss, char
**job, lsm_flag flags);

five arguments. no cap. let's go through them one by one like a group chat roll call πŸ“‹


πŸ¦‹ ARGUMENTS πŸ¦‹

  • conn β€” a Valid connection. like, it has to actually be valid. don't be out here passing vibes. ✨
  • fs β€” Pointer of lsm_fs. that's your file system, the whole point of the operation.
  • ss β€” Pointer of lsm_fs_ss to delete. this is the snapshot. the main character of this function. she's getting deleted. πŸ’€
  • job β€” Output pointer of string. okay so if your storage system supports asynchronous action on this, a job gets created and you can track it via lsm_job_status_get. and if the storage system does not support asynchronous action on this? then it's NULL. no job, no tracking, just done. lowkey efficient fr fr
  • flags β€” Reserved for future use, must be LSM_CLIENT_FLAG_RSVD. like, you don't get to freestyle here bestie. it's reserved. put the right flag. πŸ™ˆ

πŸ’œ VERSION πŸ’œ

1.0 β€” she's been here since 1.0 and she's still serving.


πŸ”₯ DESCRIPTION πŸ”₯

Deletes the specified file system snapshot. that's it. that's the tea. β˜• one snapshot, gone, bye bye, no notes. 🌈


πŸ‘‘ CAPABILITY πŸ‘‘

LSM_CAP_FS_SNAPSHOT_DELETE

if your storage system has this capability, you're good to go. if it doesn't… vibe check failed, sorry babe 😭


⭐ RETURN ⭐

Error code as enumerated by lsm_error_number. here's the whole roster, no skipping, we don't gatekeep:

  • LSM_ERR_OK
    • On success. we ate. πŸ’…
  • LSM_ERR_JOB_STARTED
    • A job is started. Please check the job output pointer. like actually check it, don't just leave it sitting there 🫢
  • LSM_ERR_INVALID_ARGUMENT
    • When any argument is NULL or not a valid lsm_connect pointer or invalid flags. basically: something was sus. not in a fun way. πŸ™ˆ
  • LSM_ERR_NOT_FOUND_FS
    • When file system not found. she's not here. nobody's home. 😭
  • LSM_ERR_NOT_FOUND_FS_SS
    • When file system snapshot not found. you're trying to delete a snapshot that doesn't exist bestie. respectfully, what are we doing πŸ’€
  • LSM_ERR_NO_SUPPORT
    • Not supported. the storage system said "no thank you" and honestly we respect the boundary.

lowkey reminder: always check that return value. LSM_ERR_OK is the dream, LSM_ERR_JOB_STARTED means go look at your job pointer, and anything else is the universe telling you to double-check your arguments. 🧚

and that's the whole page!! written by the Libstoragemgmt C API Manual, February 2026 edition, and this little function is filed under lsm_fs_ss_delete β€” see you in the next one, stay hydrated, keep your pointers valid πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from