lsm_fs_ss_create(3)

💖 lsm_fs_ss_create — bestie's guide to making a filesystem snapshot 💖

okay so this is lsm_fs_ss_create, a function from the Libstoragemgmt C API manual (section 3, the library functions section, iykyk). it does exactly one iconic thing and it does it well: it creates a file system snapshot. that's it. that's the vibe. ✨

---

🦋 SYNOPSIS 🦋

int lsm_fs_ss_create (lsm_connect *conn, lsm_fs *fs, const char *name,
lsm_fs_ss **snapshot, char **job, lsm_flag flags);

she takes six things and returns an int, and honestly? she's serving. let's meet the cast 👑

---

🎀 ARGUMENTS 🎀

• conn — a valid connection. no connection, no snapshot, no slay. 💅
• fs — pointer of lsm_fs to create snapshot. this is the filesystem we're snatching a snapshot of, bestie.
• name — string. a human recognizable name, but heads up: it might be altered or ignored by certain storage system. not every storage system respects your naming choices, and that's just the reality of it. 😭
• snapshot — output pointer of lsm_fs_ss for newly created snapshot. this is where the fresh new baby gets handed back to you 🫶
• 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_ss_get. NULL if storage system does not support asynchronous action on this. so if you get a job back, go track it, don't just leave it on read. 📱
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. it's giving "no thoughts, just reserved". don't put anything else in there, fr fr.

---

🌸 VERSION 🌸

1.0 — she's been here since the beginning, a true original.

---

✨ DESCRIPTION ✨

Creates a new file system snapshot. that's the whole thing. short, sweet, main character energy. 💖

---

👑 CAPABILITY 👑

LSM_CAP_FS_SNAPSHOT_CREATE

this is the capability flag you're looking for. if your storage system doesn't have it, this function is not gonna eat, sorry bestie. 🥲

---

💀 RETURN 💀

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

• LSM_ERR_OK — On success. we ate and left no crumbs. 🎉
• LSM_ERR_JOB_STARTED — A job is started. Please check the job output pointer. she's running in the background, go check on her!
• LSM_ERR_INVALID_ARGUMENT — When any argument is NULL or not a valid lsm_connect pointer or invalid flags. bestie, something you handed her was not it. 🙈
• LSM_ERR_NOT_FOUND_FS — When file system not found. where is she? gone. vanished. not found. 😭
• LSM_ERR_NOT_ENOUGH_SPACE — Pool does not have enough space. the pool said "I have nothing left to give". 💀
• LSM_ERR_POOL_NOT_READY — Pool is not ready for volume creation. she needs a minute, give her a minute. 🧚
• LSM_ERR_NO_SUPPORT — Not supported. this storage system simply does not do that. periodt. 🚫

heads up bestie: this function returns an int error code, so always check it. do not ignore the return value, do not pass go, do not collect $200. 👀

---

that's the whole page!! every flag, every pointer, every error code, all present and accounted for, no cap. 💜

this lil masterpiece came from the Libstoragemgmt C API Manual, and the footer vibes were giving February 2026 with lsm_fs_ss_create all over the place. bye bestie, go snapshot something 🌈💅🦋