lsm_fs_delete(3)

💖 lsm_fs_delete — bestie's guide to the Libstoragemgmt C API Manual 💖

okay so. welcome to lsm_fs_delete(3), a manual page from the Libstoragemgmt C API Manual and literally one of the most "are you SURE" functions in the whole library. it deletes a file system. the whole thing. all of it. we're gonna walk through it together because I refuse to let you rawdog this call, bestie 🫶

---

✨ NAME ✨

lsm_fs_delete — deletes a file system. that's it. that's the vibe. 💅

---

🦋 SYNOPSIS 🦋

int lsm_fs_delete (lsm_connect *conn, lsm_fs *fs, char **job, lsm_flag flags);

---

🌸 ARGUMENTS 🌸

• conn — a valid connection. like, actually valid. no funny business.
• fs — the pointer of the lsm_fs that is to be deleted. your main character. about to exit stage left.
• 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.
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. that's the whole rule. don't get creative with it 🙈

---

⭐ VERSION ⭐

1.0

---

🔥 DESCRIPTION 🔥

Deletes a file system and its data is lost! not "moved to trash". not "recoverable in 30 days". lost. say it with me. 😭

and it's not just the file system, bestie, it's the whole extended friend group:

• when the file system has snapshot attached, all its snapshot will be deleted also.
• when the file system is exported, all its exports will be deleted also.

if the specified file system is has child dependency, it cannot be deleted. nope. not happening. the way it will just refuse you 💀. so you may use lsm_fs_child_dependency and lsm_fs_child_dependency_delete before lsm_fs_delete — clean up your little dependency situations first, then come back and do the deed. iykyk.

fr fr: this is a destructive call. read the paragraph above twice. then read it again. then call it.

---

👑 CAPABILITY 👑

LSM_CAP_FS_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.
• LSM_ERR_INVALID_ARGUMENT — when any argument is NULL or not a valid lsm_connect pointer or invalid flags.
• LSM_ERR_NOT_FOUND_FS — when file system not found. it's giving "who?"
• LSM_ERR_POOL_NOT_READY — pool is not ready.
• LSM_ERR_NO_SUPPORT — not supported.
• LSM_ERR_HAS_CHILD_DEPENDENCY — specified volume has child dependencies. (yes, it says volume, we're all just living here.)

---

that's the whole page, bestie 🎀 go forth, pass LSM_CLIENT_FLAG_RSVD, and maybe double-check those child dependencies first. this has been the Libstoragemgmt C API Manual page lsm_fs_delete(3), from the lsm_fs_delete source, dated February 2026. mwah. 💖🦋🧚💜