lsm_volume_delete(3)

💖 lsm_volume_delete — bestie edition 💖

okay so this is lsm_volume_delete(3) from the Libstoragemgmt C API Manual, and she's here to help you yeet a volume into the void. buckle up, because there's a lil bit of prep work before you're allowed to do that. 🎀

---

✨ NAME ✨

lsm_volume_delete — Delete a volume. that's it. that's the whole job. she deletes. 💅

---

🌸 SYNOPSIS 🌸

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

---

🦋 ARGUMENTS 🦋

• conn — a valid lsm_connect pointer. like, actually valid, bestie, we're checking. 👀
• volume — pointer to the lsm_volume that's getting deleted. rip to her fr fr. 💀
• 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 doesn't support asynchronous action on this. so like, sometimes there's a job, sometimes there's just vibes. 🤷
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. no touching, no customizing, it's not that girl yet. 🙈

---

💜 VERSION 💜

1.0

---

🔥 DESCRIPTION 🔥

Deletes a volume/LUN — and heads up, its data is lost! 😭 like, gone gone. no undo button, no recycle bin, no "wait actually". periodt.

If the specified volume is masked to any access_group, it cannot be deleted. so before you come for her, you may wanna use lsm_access_groups_granted_to_volume and lsm_volume_unmask before lsm_volume_delete. unmask first, then delete. that's the order. 🫶

Also, if the specified volume has child dependency, it cannot be deleted either. you may use lsm_volume_child_dependency and lsm_volume_child_dependency_delete before lsm_volume_delete. handle the dependents first or she's not going anywhere, iykyk. 👑

seriously though — data loss is not a vibe. double, triple, quadruple check before you run this. ⚠️

---

🌈 CAPABILITY 🌈

LSM_CAP_VOLUME_DELETE

---

⭐ RETURN ⭐

error code as enumerated by lsm_error_number. here's the whole roster, no skips:

• LSM_ERR_OK — on success. slay! 🎉
• LSM_ERR_JOB_STARTED — a job is started. please check the job output pointer. she's running in the background, bestie. 🏃‍♀️
• LSM_ERR_INVALID_ARGUMENT — when any argument is NULL or not a valid lsm_connect pointer or invalid flags. 🙈
• LSM_ERR_NOT_FOUND_VOLUME — when volume not found. where is she. 🔍
• LSM_ERR_POOL_NOT_READY — pool is not ready. give her a minute. 😴
• LSM_ERR_NO_SUPPORT — not supported. 💀
• LSM_ERR_HAS_CHILD_DEPENDENCY — specified volume has child dependencies. she has responsibilities, she can't just leave. 😭

---

k that's the whole page, you ate that. mwah. 💖

this was Libstoragemgmt C API Manual, version 1.0, dated February 2026 — and yeah, lsm_volume_delete(3) is literally the same name twice in the footer, she's her own icon. ✨ bye bestie, go delete responsibly! 🎀🦋