lsm_fs_create(3)

💖 lsm_fs_create — the "make me a whole new file system" page 💖

okay bestie, welcome to the lsm_fs_create(3) glow-up ✨ this one lives in the Libstoragemgmt C API Manual and it's giving "let's manifest a brand new file system" energy. sit down, grab a strawberry 🍓, and let's get into it.

---

✨ NAME ✨

lsm_fs_create — creates a new file system 🎀

---

🌸 SYNOPSIS 🌸

int lsm_fs_create (lsm_connect *conn, lsm_pool *pool, const char *name,
uint64_t size_bytes, lsm_fs **fs, char **job, lsm_flag flags);

---

🦋 ARGUMENTS 🦋

• conn — a valid connection. like, an actual one. no fake ones allowed 💅
• pool — a pointer to an lsm_pool. this is the pool you're pulling from.
• name — string. a human-recognizable name. heads up though: certain storage systems might alter it or straight up ignore it 🙈 so don't get too attached.
• size_bytes — uint64_t. the size of your new file system, in bytes. lowkey important: the actual size might end up bigger than what you asked for, because it gets based on array rounding to block size. so don't be shocked bestie, that's just how the blocks round ✨
• fs — output pointer of lsm_fs. it'll be NULL if the storage system supports asynchronous action on this. and listen — the returned value must be freed with lsm_fs_record_free. don't leave it hanging, that's not the vibe 😭
• 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_fs_get. it's NULL if the storage system doesn't support async on this. no job, no tracking, no problem.
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. periodt. don't try anything else 🚫

---

👑 VERSION 👑

1.0 — the classic, the icon, the blueprint 🌈

---

💅 DESCRIPTION 💅

Creates a new file system for NFS or CIFS share. that's it, that's the whole serve. you asked, it delivers, main character energy 🫶

---

⭐ CAPABILITY ⭐

LSM_CAP_FS_CREATE

like yes, this is literally the capability you need for this to even be a thing 💫

---

🔥 RETURN 🔥

LSM_ERR_OK on success, LSM_ERR_JOB_STARTED if async.

• LSM_ERR_OK
  • On success. we love a happy ending 💖
• LSM_ERR_JOB_STARTED
  • A job is started. Please check the 'job' output pointer. yes, that job pointer. go look at it 👀
• LSM_ERR_INVALID_ARGUMENT
  • When any argument is NULL or not a valid lsm_connect pointer or invalid flags. basically: something in there was not it 💀
• LSM_ERR_NOT_FOUND_POOL
  • When pool not found. where is she. where did she go 😭
• LSM_ERR_NOT_ENOUGH_SPACE
  • Pool does not have enough space. the math wasn't mathing, bestie 🍓
• LSM_ERR_POOL_NOT_READY
  • Pool is not ready for file system creation. she needs a minute. let her breathe 🧚
• LSM_ERR_NO_SUPPORT
  • Not supported. respectfully, no 🙅

ngl, if you get an error back, actually read it before you spiral — every one of these is telling you exactly what's wrong 💜

---

and that's the whole page, bestie! this was lsm_fs_create from the Libstoragemgmt C API Manual, version 1.0, dated February 2026 🌸 go forth and create file systems responsibly, and remember: free your lsm_fs records. mwah 💋✨