lsm_acces...oup_delete(3)

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

πŸ’– lsm_access_group_delete β€” from the Libstoragemgmt C API Manual, section 3 πŸ’–

okay bestie, gather round, because we're deleting an access group and we're doing it correctly. this is lsm_access_group_delete, and yes it's giving main character energy for a function whose whole job is yeeting a group into the void 🫢


✨ NAME ✨

lsm_access_group_delete β€” deletes an access group. that's it, that's the whole vibe. bye girl πŸ’…


✨ SYNOPSIS ✨

int lsm_access_group_delete (lsm_connect *conn, lsm_access_group
*access_group, lsm_flag flags);

✨ ARGUMENTS ✨

  • conn β€” a valid lsm_connect pointer. like, actually valid. don't be weird about it πŸŽ€
  • access_group β€” pointer to the lsm_access_group that's getting deleted. this is your target, your girl, your moment ✨
  • flags β€” reserved for future use, so it must be LSM_CLIENT_FLAG_RSVD. no freestyling. the future hasn't happened yet 🌸

✨ VERSION ✨

1.0 β€” baby's first version number, iconic, no notes πŸ’œ


✨ DESCRIPTION ✨

So. This function deletes an access group. That's the whole plot. πŸ”₯

BUT β€” and this is the part where you lean in β€” only an access group with no volume masked can be deleted. if a volume is still masked to it, it's not going anywhere. it's booked and busy. the group stays. periodt πŸ’€


✨ CAPABILITY ✨

LSM_CAP_ACCESS_GROUP_DELETE β€” check for this before you go deleting things, iykyk 🌈


✨ RETURN ✨

It hands you back an error code, as enumerated by lsm_error_number. the whole roster, no skips:

  • LSM_ERR_OK β€” on success. we ate. πŸ‘‘
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL, or it's not a valid lsm_connect pointer, or the flags are invalid. basically: something you passed was a mess πŸ™ˆ
  • LSM_ERR_NOT_FOUND_ACCESS_GROUP β€” when the access group isn't found. she's not here, bestie 😭
  • LSM_ERR_IS_MASKED β€” when the access group has a volume masked. blocked. locked down. can't delete her πŸ¦‹
  • LSM_ERR_NO_SUPPORT β€” not supported. the machine said no πŸ’€
fr fr, check that return value. not every delete is a slay and the code will absolutely tell on you.

that's the whole page, angel πŸ’– go forth and delete responsibly (or don't delete, if the volume's masked, which is literally the whole rule) 🧚

β€” with love from the Libstoragemgmt C API Manual, lsm_access_group_delete(3), February 2026 edition, version 1.0 πŸŽ€βœ¨

πŸ“¦ where this page comes from