lsm_acces...oup_delete(3)
π 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 validlsm_connectpointer. like, actually valid. don't be weird about it πaccess_groupβ pointer to thelsm_access_groupthat's getting deleted. this is your target, your girl, your moment β¨flagsβ reserved for future use, so it must beLSM_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 isNULL, or it's not a validlsm_connectpointer, 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
- fedora 43: libstoragemgmt-devel 1.10.3-1.fc43 Β· LGPL-2.1-or-later
- fedora 44: libstoragemgmt-devel 1.10.3-1.fc44 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms