lsm_fs_clone(3)

💖 lsm_fs_clone — bestie, we're cloning a filesystem 💖

okay so this is a page from the Libstoragemgmt C API Manual, section 3, and the function is called lsm_fs_clone. It's giving "duplicate my filesystem but make it ✨efficient✨". Let's get into it.

---

✨ NAME ✨

lsm_fs_clone — Clones an existing file system. That's it, that's the whole vibe. 🦋

---

🌸 SYNOPSIS 🌸

int lsm_fs_clone (lsm_connect *conn, lsm_fs *src_fs, const char *name,
lsm_fs_ss *optional_ss, lsm_fs **cloned_fs, char **job, lsm_flag flags);

---

💅 ARGUMENTS 💅

• conn — a valid connection, bestie. Gotta have one. Valid connection.
• src_fs — pointer of lsm_fs for the source file system. Like, the original. The blueprint. The main character we're copying. 👑
• name — a string. Human recognizable name for the new file system — but heads up, it might be altered or ignored by certain storage system. So don't get too attached to your naming skills, some storage systems just do their own thing. 🙈
• optional_ss — pointer of lsm_fs_ss. This is the file system snapshot to base the clone from. Set to NULL of not needed.. (yes that typo is canon, we don't fix what we don't own 💀)
• cloned_fs — output pointer of lsm_fs for the newlly created file system. Will be NULL if the storage system support asynchronous action on this. The returned value must be freed with a call to lsm_fs_record_free. Don't forget, or that's a memory leak and we don't do those. 🫶
• job — output pointer of string. If the storage system support asynchronous action on this, a job will be created and could be tracked via lsm_job_status_fs_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. No freelancing with the flags, bestie. 🎀

---

⭐ VERSION ⭐

1.0 — iconic from day one, honestly.

---

🦋 DESCRIPTION 🦋

Create a point in time read writeable space efficient copy of the specified file system — also know as a read writeable snapshot. The new file system will reside in the same pool of the specified file system. Same pool, same energy, different filesystem. periodt. 💜

---

🔥 CAPABILITY 🔥

LSM_CAP_FS_CLONE

---

🌈 RETURN 🌈

Error code as enumerated by lsm_error_number. Let's go through them:

• 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. So like, don't do that.
• LSM_ERR_NOT_FOUND_FS
  • When file system not found. she's not here. 😭
• LSM_ERR_NOT_ENOUGH_SPACE
  • Pool does not have enough space. The pool said no. 💀
• LSM_ERR_POOL_NOT_READY
  • Pool is not ready. Give her a minute. 🧚
• LSM_ERR_NO_SUPPORT
  • Not supported. Not every storage system woke up and chose functionality, iykyk. 🙈

---

🎀 SIGN-OFF 🎀

This page lives under the Libstoragemgmt C API Manual, dated February 2026, and it's filed as lsm_fs_clone(3). Go clone something responsibly, bestie. mwah. 💖💅