lsm_volum...ate_range(3)

✨ NAME ✨

lsm_volume_replicate_range — bestie, it replicates a portion of a volume to a volume. That's it, that's the whole vibe. 💖

Oh and btw, this lil cutie lives in the Libstoragemgmt C API Manual — you're in the right place, iykyk. 🫶

---

🌸 SYNOPSIS 🌸

int lsm_volume_replicate_range (lsm_connect *conn, lsm_replication_type rep_type, lsm_volume *source, lsm_volume *dest, lsm_block_range **ranges, uint32_t num_ranges, char **job, lsm_flag flags);

---

🎀 ARGUMENTS 🎀

okay so here's the cast of characters, no skips, we're doing all of them:

• conn — a valid connection. gotta have one, queen. 👑
• rep_type — an lsm_replication_type. the valid values are literally:
  • LSM_VOLUME_REPLICATE_CLONE — a point in time read writeable space efficient copy of data. also known as a read writeable snapshot. ✨
  • LSM_VOLUME_REPLICATE_COPY — a full bitwise copy of the data, and yes it occupies full space. no shortcuts, no diet version, the whole thing. 💅
• source — pointer of the replication source lsm_volume. the origin story. 🌱
• dest — pointer of the replication target lsm_volume. plot twist: it could be the same as source. 🤯
• ranges — array of lsm_block_range. please please please use lsm_block_range_record_array_alloc and lsm_block_range_record_alloc to create it. don't freehand this one, bestie. 🙈
• num_ranges — uint32_t. the number of entries in ranges. count them. 📏
• job — output pointer of string. if the storage system supports asynchronous action on this, a job will be created and could be tracked via lsm_job_status_get. it's NULL if the storage system does not support asynchronous action on this. so like, sometimes you get a job, sometimes you don't, we don't make the rules. 😭
• flags — reserved for future use, must be LSM_CLIENT_FLAG_RSVD. it's giving "placeholder but make it mandatory". 🚧

---

⭐ VERSION ⭐

1.0

---

🦋 DESCRIPTION 🦋

Replicates a portion of specified source volume to target volume. just a portion, not the whole thing — that's the moment, that's the main character energy. 🔥

---

🌈 CAPABILITY 🌈

LSM_CAP_VOLUME_COPY_RANGE LSM_CAP_VOLUME_COPY_RANGE_CLONE
LSM_CAP_VOLUME_COPY_RANGE_COPY

---

💜 RETURN 💜

error code as enumerated by lsm_error_number. here's the whole lineup:

• LSM_ERR_OK
  • on success. we ate. 🎉
• 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 or invalid replication type. basically: something's not right and we're telling you. 💀
• LSM_ERR_NOT_FOUND_VOLUME
  • when volume not found. it's not there. gone. 🫥
• LSM_ERR_NOT_FOUND_POOL
  • when pool not found. also not there. 😔
• LSM_ERR_POOL_NOT_READY
  • pool is not ready. give it a minute, it's getting ready. 🧖
• LSM_ERR_NO_SUPPORT
  • not supported. respectfully, nope. 🙅

no cap: these are the exact codes, so don't go inventing new ones, bestie. the manpage said what it said. 💖

---

and that's the whole page, periodt. 🌟 this was the lsm_volume_replicate_range page from the Libstoragemgmt C API Manual, dated February 2026 — mwah, take care of her, she's iconic. 👑💅✨