lsm_volum...cy_delete(3)

💖 NAME 💖

lsm_volume_child_dependency_delete — ok so bestie, this one deletes all the child dependencies of the volume you point at. Like, every single one. No cap. 🦋

---

✨ SYNOPSIS ✨

int lsm_volume_child_dependency_delete (lsm_connect *conn, lsm_volume
*volume, char **job, lsm_flag flags);

---

🎀 ARGUMENTS 🎀

• conn — a valid connection, periodt. Gotta be a real one.
• volume — a pointer to an lsm_volume. That's the one whose children we're about to yeet.
• job — output pointer of string. If the storage system supports asynchronous action on this, a job gets created and you can track it via lsm_job_status_get. It's NULL if the storage system does not support asynchronous action on this. So basically: check it, don't assume. 👀
• flags — reserved for future use, so it literally must be LSM_CLIENT_FLAG_RSVD. Not vibes. Must be.

---

💅 VERSION 💅

1.0

---

🌸 DESCRIPTION 🌸

So here's the tea: you're instructing the storage system to remove all child dependencies of the specified volume — and the way it does that is by duplicating the required storage before breaking the replication relationship. The way it just handles the copy first and then the breakup? Iconic behaviour honestly. 💖

---

👑 CAPABILITY 👑

LSM_CAP_VOLUME_CHILD_DEPENDENCY_RM

---

🔥 RETURN 🔥

Error code as enumerated by lsm_error_number. Here's the whole roster, no skipping:

• LSM_ERR_OK — on success. Slay. ✨
• LSM_ERR_JOB_STARTED — a job is started, so please go check the job output pointer. It's right there bestie, look at it.
• LSM_ERR_INVALID_ARGUMENT — when any argument is NULL, or it's not a valid lsm_connect pointer, or the flags are invalid, or the lsm_volume pointer is invalid. Basically something in the group chat is not passing the vibe check.
• LSM_ERR_NOT_FOUND_VOLUME — when the volume is not found. Can't delete the children of a volume that isn't there, bestie. 😭
• LSM_ERR_NO_STATE_CHANGE — when the volume is not a replication source. No source, no child dependencies, nothing to change.
• LSM_ERR_NO_SUPPORT — not supported. 💀

Heads up: these are error codes from the lsm_error_number enum — treat them as the real deal, not decorative.

---

ok that's the whole page, you ate that fr fr 🫶 this was from the Libstoragemgmt C API Manual, version vibes from February 2026 — go forth and delete responsibly, mwah 💋