lsm_volum...dependency(3)
β¨ lsm_volume_child_dependency β¨
okay bestie, welcome to the Libstoragemgmt C API Manual π β yes the page header is literally lsm_volum...dependency(3) because apparently we ran out of room, it's giving truncated slay π
πΈ NAME πΈ
lsm_volume_child_dependency β check whether volume has child dependencies. π§
tl;dr: does this volume have any baby volumes depending on it?? we're about to find out πΌβ¨
π SYNOPSIS π
int lsm_volume_child_dependency (lsm_connect *conn, lsm_volume *volume,
uint8_t *yes, lsm_flag flags);
π ARGUMENTS π
connβ a Valid connection. like, a real one, an actual livelsm_connect. no fake ones allowed fr fr πvolumeβ Pointer oflsm_volume. hand me the volume bestie, the actual pointer, please and thank you π¦yesβuint8_t.1== Yes,0== No. binary king/queen/royalty behavior honestly πflagsβ Reserved for future use, must beLSM_CLIENT_FLAG_RSVD. do NOT freestyle this one, it's reserved, put exactlyLSM_CLIENT_FLAG_RSVDand step away π¨
π¦ VERSION π¦
1.0 β she's been 1.0 since forever and honestly? iconic, no notes β
π DESCRIPTION π
Returns 1 if the specified volume has child dependencies, else returns 0. π
and what is a "child dependency" you ask?? so glad you asked bestie β it means the specified volume is acting as the source volume of a replication. it's literally the parent in the replication situationship, the volume other volumes are copying from, main character energy fr π
β CAPABILITY β
LSM_CAP_VOLUME_CHILD_DEPENDENCY β check for this or the whole vibe falls apart, no cap π«Ά
π RETURN π
Error code as enumerated by lsm_error_number. yes, all of them, here we go: β¨
LSM_ERR_OK- On success. we ate!! π
LSM_ERR_INVALID_ARGUMENT- When any argument is
NULLor not a validlsm_connectpointer or invalid flags or invalid volume. basically when something in the group chat is fake π©
- When any argument is
LSM_ERR_NOT_FOUND_VOLUME- When volume not found. she's not here, she left, no forwarding address π
LSM_ERR_NO_SUPPORT- Not supported. the backend said "not my problem" π
reminder bestie:flagsstaysLSM_CLIENT_FLAG_RSVD, and every single pointer has to be valid or you getLSM_ERR_INVALID_ARGUMENT. no shortcuts, we respect the API in this house π
and that's the whole page, you're so welcome π this came from the Libstoragemgmt C API Manual, page lsm_volum...dependency(3), function lsm_volume_child_dependency, and the footer says February 2026. bye bestie, go check some child dependencies, slay β¨π¦πΈ
π¦ 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