lsm_pool_status_get(3)

✨ NAME ✨

okay so bestie, gather round 💖 this is lsm_pool_status_get from the Libstoragemgmt C API Manual — it retrieves the status of a specified pool. that's it, that's the whole job, and it does it flawlessly 💅

---

🌸 SYNOPSIS 🌸

uint64_t lsm_pool_status_get (lsm_pool *s);

🎀 ARGUMENTS 🎀

• s — the Pool you want the status of. like, the pool. the one. main character pool 👑

---

🦋 VERSION 🦋

1.0 — vintage, but make it iconic ✨

---

💖 DESCRIPTION 💖

It retrieves the status of the specified pool. no cap. that's the vibe, that's the function, she's simple and she serves 🫶

---

🌈 RETURN 🌈

She hands you back a uint64_t — the status of the specified pool — and heads up, this field is bit sensitive 🚨 so pay attention bestie. The possible values are:

• LSM_POOL_STATUS_UNKNOWN — the plugin literally failed to query out the status of the Pool. it tried, it fumbled, we don't know 😭
• LSM_POOL_STATUS_OK — the data of this pool is accessible with not data lose. BUT it might come along with LSM_POOL_STATUS_DEGRADED to indicate redundancy lose. so like, data's fine but the safety net is not safety netting 🪢
• LSM_POOL_STATUS_OTHER — vendor specific status, iykyk. the status_info property will explain the detail 👀
• LSM_POOL_STATUS_DEGRADED — Pool is lost data redundancy due to I/O error or offline of one or more RAID member. often comes with LSM_POOL_STATUS_OK to indicate data is still accessible with not data lose. Examples:
  • RAID 6 pool lost access to 1 disk or 2 disks.
  • RAID 5 pool lost access to 1 disk.
• LSM_POOL_STATUS_ERROR — Pool data is not accessible due to some members offline. Examples:
  • RAID 5 pool lost access to 2 disks.
  • RAID 0 pool lost access to 1 disks.
• LSM_POOL_STATUS_STARTING — Pool is reviving from STOPPED status. Pool data is not accessible yet. she's waking up, give her a sec 💀
• LSM_POOL_STATUS_STOPPING — Pool is stopping by administrator. Pool data is not accessible.
• LSM_POOL_STATUS_STOPPED — Pool is stopped by administrator. Pool data is not accessible.
• LSM_POOL_STATUS_RECONSTRUCTING — Pool is reconstructing the hash data or mirror data. mostly happens when disk revive from offline or disk replaced. Pool.status_info may contain progress of this reconstruction job. often comes with LSM_POOL_STATUS_DEGRADED and LSM_POOL_STATUS_OK. glow-up in progress ✨
• LSM_POOL_STATUS_VERIFYING — Array is running integrity check on data of current pool. it might be started by administrator or array itself. the I/O performance will be impacted. Pool.status_info may contain progress of this verification job. often comes with LSM_POOL_STATUS_OK to indicate data is still accessible.
• LSM_POOL_STATUS_GROWING — Pool is growing its size and doing internal jobs. Pool.status_info can contain progress of this growing job. often comes with LSM_POOL_STATUS_OK to indicate data is still accessible. she's thriving, she's expanding 📈
• LSM_POOL_STATUS_DELETING — Array is deleting current pool. rip bozo, it's over 😭

ngl bestie, several of these mean "Pool data is not accessible" — that is not a drill. read the value before you assume anything is fine 🙈

---

and that's the whole page, periodt 💅 this was lsm_pool_status_get from the Libstoragemgmt C API Manual, version 1.0, dated February 2026 — love that for us, mwah, bye bestie 🎀💖🦋