lsm_capabilities(3)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

✨ NAME ✨

lsm_capabilities β€” bestie, this is the one that asks the storage array what it can actually do πŸ‘‘ (query the capabilities of the storage array, fr fr)


🌸 SYNOPSIS 🌸

int lsm_capabilities (lsm_connect *conn, lsm_system *system,
lsm_storage_capabilities **cap, lsm_flag flags);

πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a valid lsm_connect pointer, like actually valid, no fake ones pls πŸ™ˆ
  • system β€” the system of interest πŸ’– the one you're curious about
  • cap β€” output pointer of lsm_storage_capabilities, aka where the storage array capabilities land. Heads up bestie: the returned value must be freed with a call to lsm_capability_record_free. Don't forget. Not me forgetting to free memory… 😭
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. Like it's reserved, so keep it reserved πŸ’…

⭐ VERSION ⭐

1.0


πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this function queries the capabilities of the storage array. The whole point of a "capability" is to tell you whether a certain piece of functionality is supported by the specified storage system πŸ‘€βœ¨

So when you're about to call some function, check what capability it requires first β€” check the desired function for its required capability. To verify a capability is actually supported, use lsm_capability_supported 🫢

And here's the lowkey important part: if some functionality is not listed in the enumerated capability type (lsm_capability_type), then that functionality is mandatory and is required to exist. Like it's not optional, it's a given, periodt πŸ’€


πŸ”₯ RETURN πŸ”₯

Error code as enumerated by lsm_error_number. The vibe check results:

  • LSM_ERR_OK
    • On success πŸŽ‰ slay
  • LSM_ERR_INVALID_ARGUMENT
    • When any argument is NULL or not a valid lsm_connect pointer or not a valid lsm_system or invalid flags πŸ™ˆ
  • LSM_ERR_NOT_FOUND_SYSTEM
    • When the specified system does not exist 😭 it's just not there bestie

That's the whole page, babe πŸ’œ β€” brought to you by the Libstoragemgmt C API Manual, version vibe lsm_capabilities(3), dated February 2026. Go forth and query those capabilities, you main character πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from