lsm_volume_unmask(3)

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

πŸ’– lsm_volume_unmask πŸ’–

okay bestie, welcome to the Libstoragemgmt C API Manual ✨ this one's called lsm_volume_unmask and it's the girl who takes the access away. yes, we're doing the revoking one. she said "you can't sit with us" but in storage terms πŸŽ€


🌸 NAME 🌸

lsm_volume_unmask β€” revokes access to a volume for the specified group

like. she un-invites the group from the volume. the mask is OFF. the party is OVER. πŸ’…


✨ SYNOPSIS ✨

int lsm_volume_unmask (lsm_connect *conn, lsm_access_group
*access_group, lsm_volume *volume, lsm_flag flags);

it hands you back an int, because of course it does, it's a C API function and they love returning ints 😭


πŸ¦‹ ARGUMENTS πŸ¦‹

  • conn β€” a valid connection. like, an actual live one. if it's NULL we're gonna have a bad time.
  • access_group β€” pointer of lsm_access_group. this is the group losing their VIP pass 🎟️
  • volume β€” pointer of lsm_volume. this is the volume that's about to become exclusive πŸ’€
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. like, that's not a suggestion bestie, that's the rule πŸ”₯

πŸ’œ VERSION πŸ’œ

1.0


🌈 DESCRIPTION 🌈

Revokes access to a volume for the specified group.

that's the whole thing. she's a one-job icon. group had access, now group does not have access, and that is genuinely the entire plot 🫢


πŸ‘‘ CAPABILITY πŸ‘‘

LSM_CAP_VOLUME_UNMASK

this is the capability check you look for, iykyk ⭐


πŸŽ€ RETURN πŸŽ€

Error code as enumerated by lsm_error_number. so like, here's the whole menu:

  • LSM_ERR_OK
    • On success. slay ✨
  • LSM_ERR_INVALID_ARGUMENT
    • When any argument is NULL or not a valid lsm_connect pointer or invalid flags or invalid lsm_access_group pointer or invalid lsm_volume.
  • LSM_ERR_NOT_FOUND_ACCESS_GROUP
    • When access group not found. she's not in the system, bestie, nowhere πŸ’€
  • LSM_ERR_NOT_FOUND_VOLUME
    • When volume not found.
  • LSM_ERR_NO_STATE_CHANGE
    • When specified volume is not masked to specified access group. like girl there's nothing to revoke, the volume was never masked to them in the first place πŸ™ˆ
  • LSM_ERR_NO_SUPPORT
    • Not supported. the system said "no ❀️"
fr fr check your return codes. every single one of them. no skipping, no assuming it worked, that's how you end up debugging at 3am 😭

and that's the whole page, bestie!! 🧚 from the Libstoragemgmt C API Manual, this little gem dropped in February 2026, and the source line at the bottom is just lsm_volume_unmask and lsm_volume_unmask(3) looking all cute together. go forth and unmask responsibly πŸ’–πŸŒΈβœ¨

πŸ“¦ where this page comes from