lsm_volume_resize(3)

🌸 NAME 🌸

lsm_volume_resize — ok so bestie, this is the one that resizes an existing volume 💖

---

✨ SYNOPSIS ✨

int lsm_volume_resize (lsm_connect *conn, lsm_volume *volume, uint64_t new_size, lsm_volume **resized_volume, char **job, lsm_flag flags);

---

🎀 ARGUMENTS 🎀

• conn — a valid lsm_connect pointer, no funny business 💅
• volume — lsm_volume. This is the volume we're gonna re-size, periodt.
• new_size — uint64_t. The new size of the volume, in bytes. Heads up though: the actual size might be bigger than what you asked for, because it gets based on array rounding to block size. So like, don't be shocked, it's giving "close enough" 😭
• resized_volume — output pointer of the updated lsm_volume. It might be NULL if the storage system supports asynchronous action on this. And listen — that memory must be freed with a call to lsm_volume_record_free. Don't leave it hanging bestie 🙈
• 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_volume_get. It'll be NULL if the storage system does not support asynchronous action on this.
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. Like, it has one job and one job only 🔥

---

💜 VERSION 💜

1.0

---

🦋 DESCRIPTION 🦋

So what this does is resize the specified volume. That's the whole vibe. ✨

But — and this is the important part — some pool might not allow volume resize at all. So please, please check lsm_pool_unsupported_actions_get for LSM_POOL_UNSUPPORTED_VOLUME_GROW and LSM_POOL_UNSUPPORTED_VOLUME_SHRINK before invoking this function. Do the vibe check first, then call. iykyk 🫶

---

👑 CAPABILITY 👑

LSM_CAP_VOLUME_RESIZE

---

🌈 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_POOL
  • When pool not found.
• LSM_ERR_NOT_FOUND_VOLUME
  • When volume not found.
• LSM_ERR_NOT_ENOUGH_SPACE
  • Pool does not have enough space. 💀
• LSM_ERR_POOL_NOT_READY
  • Pool is not ready for volume resizing.
• LSM_ERR_NO_STATE_CHANGE
  • Requested size if identical to current size.
• LSM_ERR_NO_SUPPORT
  • Not supported. 😭

---

and that's the whole page, bestie — written up in the Libstoragemgmt C API Manual, the lsm_volume_resize(3) one, dated February 2026. go resize something responsibly, ily 🫶✨