lsm_block...array_free(3)

💖 lsm_block_range_record_array_free — the manual page, bestie edition 💖

okay so you're in the Libstoragemgmt C API Manual, section 3 — that's the C library functions girlies. and we're talking about lsm_block_range_record_array_free(3) today. pull up a chair. 🫶

---

✨ NAME ✨

lsm_block_range_record_array_free — frees the memory of an lsm_block_range array. that's it. that's the whole job. she's a cleanup queen and she eats every time 💅

---

✨ SYNOPSIS ✨

#include <libstoragemgmt/libstoragemgmt.h>

int lsm_block_range_record_array_free (lsm_block_range *br[], uint32_t size);

---

✨ ARGUMENTS ✨

• br[] — the array you want to release memory for. hand it over, bestie, she'll take it from here 🎀
• size — how many elements are in that array. she needs the count, no guessing games.

---

✨ VERSION ✨

1.0 — yes she's been iconic since day one, no cap 🌈

---

✨ DESCRIPTION ✨

Frees the memory resources for an array of lsm_block_range. you built the array, you filled it up, and now you gotta let it go. this is the letting-go function. closure, literally. ✨

---

✨ RETURN ✨

she returns an error code, and the codes come from lsm_error_number:

• LSM_ERR_OK — slayed. success, or not found. either way, we're chill 😌
• LSM_ERR_INVALID_ARGUMENT — this is the vibe check FAILING. it happens when any argument is NULL or isn't a valid lsm_block_range pointer. so like… don't do that 🙈

fr fr, if you pass her garbage she will tell you, but she will not clean it up. valid pointers only, bestie.

---

and that's the whole page, periodt 👑

sign-off time: this lil masterpiece is from the Libstoragemgmt C API Manual, version 1.0, dated February 2026. mwah. go free your arrays responsibly 💖🦋🌸