lsm_fs_ch...cy_delete(3)

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

πŸ’– lsm_fs_child_dependency_delete β€” the one where we yeet a filesystem's whole child-dependency situation πŸ’…

okay so bestie, this one lives in the Libstoragemgmt C API Manual (manual name, noted, love that for us) and it's filed under lsm_fs_child_dependency_delete(3). Let's get into it ✨


🌸 SYNOPSIS 🌸

int lsm_fs_child_dependency_delete (lsm_connect *conn, lsm_fs *fs,
lsm_string_list *files, char **job, lsm_flag flags);

that's the whole vibe. four args and a flag, no cap 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a Valid connection. like, it has to actually be valid, we're not playing games here πŸ’€
  • fs β€” Point of lsm_fs to remove dependencies for. this is the filesystem whose children we're about to un-depend (yes that's a word now).
  • files β€” Pointer of lsm_string_list. Only work on specific files if defined. If NULL, just work on all files in this file system. so: give it a list and it's picky, give it NULL and it does everything ✨
  • job β€” Output pointer of string. If storage system support asynchronous action on this, a job will be created and could be tracked via lsm_job_status_get. NULL if storage system does not support asynchronous action on this. so check it, bestie πŸ‘€
  • flags β€” Reserved for future use, must be LSM_CLIENT_FLAG_RSVD. don't get creative with it, it's literally reserved πŸ™ˆ

πŸ’œ VERSION πŸ’œ

1.0 β€” vintage but iconic, she's been here a minute πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

Deletes child dependencies by duplicating the required storage to remove. that's the whole move. we copy the storage we need, then the dependencies go poof πŸ’…


⚠️ NOTE ⚠️

This could take a long time to complete based on dependencies. like, go make a snack, hydrate, touch some grass β€” it'll be here when you get back πŸ˜­πŸ“

πŸ‘‘ CAPABILITY πŸ‘‘

these are the capability flags you're looking for, no cap:

  • LSM_CAP_FS_CHILD_DEPENDENCY_RM
  • LSM_CAP_FS_CHILD_DEPENDENCY_RM_SPECIFIC_FILES

🌈 RETURN 🌈

Error code as enumerated by lsm_error_number. here's the full menu, don't skip any:

  • LSM_ERR_OK β€” On success. slay, we ate πŸ’…
  • LSM_ERR_JOB_STARTED β€” A job is started. Please check the job output pointer. main character energy, it's doing its own thing now πŸ”₯
  • LSM_ERR_NOT_FOUND_FS β€” When file system not found. it's giving "who? never heard of her" πŸ’€
  • LSM_ERR_NO_STATE_CHANGE β€” When file system has no child dependency. nothing to delete, nothing changed, we simply sat there 🧚

okay that's the whole page, you're basically a filesystem dependency expert now ⭐

this gorgeous little manual is from the Libstoragemgmt C API Manual, version February 2026 β€” ty for coming to my ted talk, mwah πŸ’–πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from