lsm_pool_member_info(3)

💖 lsm_pool_member_info — the libstoragemgmt C API manual, bestie edition 💖

okay so this one lives in the Libstoragemgmt C API Manual, and it's called lsm_pool_member_info. It's giving "tell me who's in this pool's friend group" energy. Let's go 🫶

---

✨ NAME ✨

lsm_pool_member_info — retrieves the membership of given pool.

like. literally who is in this pool. who are its people. 💅

---

🌸 SYNOPSIS 🌸

int lsm_pool_member_info (lsm_connect *conn, lsm_pool *pool,
lsm_volume_raid_type *raid_type, lsm_pool_member_type *member_type,
lsm_string_list **member_ids, lsm_flag flags);

---

🎀 ARGUMENTS 🎀

• conn — a valid connection. it has to be real, bestie, no imaginary friends.
• pool — the pointer of lsm_pool. the pool we're investigating 👀
• raid_type — an lsm_volume_raid_type. the valid values are, and I'm listing every single one because we don't gatekeep:
  • LSM_VOLUME_RAID_TYPE_RAID0 — Stripe.
  • LSM_VOLUME_RAID_TYPE_RAID1 — Two disks Mirror
  • LSM_VOLUME_RAID_TYPE_RAID3 — Byte-level striping with dedicated parity
  • LSM_VOLUME_RAID_TYPE_RAID4 — Block-level striping with dedicated parity
  • LSM_VOLUME_RAID_TYPE_RAID5 — Block-level striping with distributed parity
  • LSM_VOLUME_RAID_TYPE_RAID6 — Block-level striping with two distributed parities, aka, RAID-DP
  • LSM_VOLUME_RAID_TYPE_RAID10 — Stripe of mirrors
  • LSM_VOLUME_RAID_TYPE_RAID15 — Parity of mirrors
  • LSM_VOLUME_RAID_TYPE_RAID16 — Dual parity of mirrors
  • LSM_VOLUME_RAID_TYPE_RAID50 — Stripe of parities
  • LSM_VOLUME_RAID_TYPE_RAID60 — Stripe of dual parities
  • LSM_VOLUME_RAID_TYPE_RAID51 — Mirror of parities
  • LSM_VOLUME_RAID_TYPE_RAID61 — Mirror of dual parities
  • LSM_VOLUME_RAID_TYPE_JBOD — Just bunch of disks, no parity, no striping. chaotic. iconic. no notes.
  • LSM_VOLUME_RAID_TYPE_UNKNOWN — The plugin failed to detect the volume's RAID type. 😭
  • LSM_VOLUME_RAID_TYPE_MIXED — This volume contains multiple RAID settings.
  • LSM_VOLUME_RAID_TYPE_OTHER — Vendor specific RAID type
• member_type — an lsm_pool_member_type. valid values, again, all of them:
  • LSM_POOL_MEMBER_TYPE_POOL — Current pool (also known as sub-pool) is allocated from other pool (parent pool). The 'raid_type' will set to RAID_TYPE_OTHER unless certain RAID system support RAID using space of parent pools.
  • LSM_POOL_MEMBER_TYPE_DISK — Pool is created from RAID group using whole disks.
  • LSM_POOL_MEMBER_TYPE_OTHER — Vendor specific RAID member type.
  • LSM_POOL_MEMBER_TYPE_UNKNOWN — Plugin failed to detect the RAID member type.
• member_ids — Pointer of lsm_string_list. When 'member_type' is LSM_POOL_MEMBER_TYPE_POOL, the 'member_ids' will contain a list of parent Pool IDs. When 'member_type' is LSM_POOL_MEMBER_TYPE_DISK, the 'member_ids' will contain a list of disk IDs. When 'member_type' is LSM_POOL_MEMBER_TYPE_OTHER or LSM_POOL_MEMBER_TYPE_UNKNOWN, the member_ids should be NULL. Memory need to be freed via lsm_string_list_free. 🫶 don't leak, bestie, that's not the vibe.
• flags — Reserved for future use, must be LSM_CLIENT_FLAG_RSVD. it's not for you yet, it's reserved. hands off. ✋

---

🦋 VERSION 🦋

1.2.

---

💜 DESCRIPTION 💜

Retrieves the membership information of certain pool: RAID type, member type and member ids. Currently, LibStorageMgmt supports two types of pool, and they're both a little bit main character in their own way:

• Sub-pool — LSM_POOL_MEMBER_TYPE_POOL
  • Pool space is allocated from parent pool.
  • Example:
    • NetApp ONTAP volume
• Disk RAID pool — LSM_POOL_MEMBER_TYPE_DISK
  • Pool is a RAID group assembled by disks.
  • Example:
    • LSI MegaRAID disk group
    • EMC VNX pool
    • NetApp ONTAP aggregate

so like. one of them borrows space from its parent (it's giving living at home), and the other one is a whole RAID group made of actual disks. both valid. both slay. 💅

---

🌈 CAPABILITY 🌈

LSM_CAP_POOL_MEMBER_INFO

---

⭐ RETURN ⭐

Error code as enumerated by 'lsm_error_number'. the whole roster:

• LSM_ERR_OK — On success. 🎉 we ate.
• LSM_ERR_INVALID_ARGUMENT — When any argument is NULL or invalid flags.
• LSM_ERR_NO_SUPPORT — Not supported. 💀

---

ngl bestie, if you pass a NULL anywhere or get cute with flags, LSM_ERR_INVALID_ARGUMENT is coming for you. and remember: when member_type is LSM_POOL_MEMBER_TYPE_OTHER or LSM_POOL_MEMBER_TYPE_UNKNOWN, member_ids should be NULL — and the memory you do get needs to be freed via lsm_string_list_free. periodt. ✨

---

okay that's the whole page! this dropped in February 2026, it's lsm_pool_member_info from the Libstoragemgmt C API Manual, and that's the tea. go check your pool's membership, you've got this 🧚💖