lsm_fs_resize(3)

💖 lsm_fs_resize — bestie we're resizing a file system 💖

okay so real talk, this is lsm_fs_resize(3) from the Libstoragemgmt C API Manual and it does literally exactly one thing but it does it so well. sit down, grab a strawberry, let's go 🍓

---

✨ NAME ✨

lsm_fs_resize — resizes a file system. that's it. that's the whole job. main character behavior fr 💅

---

🌸 SYNOPSIS 🌸

int lsm_fs_resize (lsm_connect *conn, lsm_fs *fs, uint64_t
new_size_bytes, lsm_fs **rfs, char **job_id, lsm_flag flags);

like. look at that signature. it's giving "i know exactly what i'm doing" ✨

---

🦋 ARGUMENTS 🦋

• conn — a valid connection. no connection, no resize, no vibes. valid only, bestie.
• fs — pointer of lsm_fs to re-size. yes it's that file system. the one you picked.
• new_size_bytes — uint64_t. the new size of the file system, in bytes. and listen — the actual size might end up bigger than what you asked for, because it gets based on the array rounding to block size. so don't come for her if it's a little thicc, that's just the math 🌈
• rfs — output pointer of the updated lsm_fs. it might be NULL if the storage system supports asynchronous action on this. so like, don't be shocked. it's not ghosting you, it's just async 😭
• job_id — output pointer of string. if the storage system supports asynchronous action on this, a job will be created and you can track it via lsm_job_status_fs_get. it's NULL if the storage system does not support asynchronous action on this. so either you get a lil tracker or you get nothing, no in between 💀
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. periodt. don't get creative with it.

---

💜 VERSION 💜

1.0 — she's been here a minute and she's thriving ✨

---

🎀 DESCRIPTION 🎀

Resize the specified file system. iconic. no notes. that is the entire description and honestly? respect 🫶

---

👑 CAPABILITY 👑

LSM_CAP_FS_RESIZE

if the storage system doesn't have this, bestie, it's not happening. check first. iykyk 💅

---

🌈 RETURN 🌈

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

• LSM_ERR_OK — on success. we love to see it. slay 💖
• LSM_ERR_JOB_STARTED — a job is started. please check the job output pointer. she's off doing her thing in the background, keep an eye on her 👀
• LSM_ERR_INVALID_ARGUMENT — when any argument is NULL or not a valid lsm_connect pointer or invalid flags. something in the group chat is wrong and it's probably the flags 🙈
• LSM_ERR_NOT_FOUND_FS — when file system not found. she's not here. she left. no forwarding address 😭
• LSM_ERR_NOT_ENOUGH_SPACE — pool does not have enough space. the pool is broke, respectfully. we've all been there 💀
• LSM_ERR_POOL_NOT_READY — pool is not ready for volume resizing. she needs a minute. let her lock in 🧚
• LSM_ERR_NO_STATE_CHANGE — requested size if identical to current size. you asked for exactly what you already have. the audacity. the commitment to nothing 🔥
• LSM_ERR_NO_SUPPORT — not supported. not today, not ever, not with that storage system 💔

real one warning: LSM_ERR_NO_STATE_CHANGE means your requested size was identical to the current size — no glow-up happened, nothing changed, and that's on the request being a carbon copy of the status quo. 💅

---

🌟 SEE ALSO 🌟

lsm_job_status_fs_get — go check that job if you got a job_id, bestie, it's right there in the arguments and it's right there in the return codes. full circle moment ⭐

---

and that's the page!! written by the Libstoragemgmt girlies, dated February 2026, living under the lsm_fs_resize name in section 3 of the Libstoragemgmt C API Manual. go resize something responsibly, queen 👑✨