lsm_block...ecord_free(3)

✨ NAME ✨

lsm_block_range_record_free — bestie, this one frees the lsm_block_range memory 💖

Like, it's the little cleanup gremlin of the Libstoragemgmt C API Manual and honestly? we love her for it.

---

🌸 SYNOPSIS 🌸

int lsm_block_range_record_free (lsm_block_range *br);

---

🎀 ARGUMENTS 🎀

• br — the record you're releasing, babes 🦋 Just hand her over and let her go.

---

⭐ VERSION ⭐

1.0 — vintage but iconic, no cap 👑

---

💅 DESCRIPTION 💅

Okay so real talk: this function frees the memory resources for a lsm_block_range. That's it. That's the whole vibe. You made a block range, you had your moment with it, and now you're freeing its memory so it can ✨ move on ✨ and so your program doesn't leak like a broken water bottle 😭

It's giving responsible memory management. Main character energy but for cleanup 🧹✨

---

🔥 RETURN 🔥

It hands you back an error code, as enumerated by lsm_error_number:

• LSM_ERR_OK — slay 💖 On success, or when the thing wasn't found.
• LSM_ERR_INVALID_ARGUMENT — when any argument is NULL, or isn't a valid lsm_block_range pointer 🙈 That one's on you, bestie.

---

Heads up gorgeous: if you pass a NULL or a not-actually-a-lsm_block_range pointer, you're getting LSM_ERR_INVALID_ARGUMENT back. The function said what it said 💀

---

Sign-off time, my love 🫶 This whole page comes straight out of the Libstoragemgmt C API Manual, it's rocking version 1.0, and it was dated February 2026. And the page itself? lsm_block_range_record_free — aka lsm_block...ecord_free(3) 💖 Free your records, hydrate, and go to bed at a reasonable hour. Periodt. 🌈