lsm_job_s...volume_get(3)
β¨ lsm_job_status_volume_get β bestie's guide to checking a job π
okay so this page lives in the Libstoragemgmt C API Manual (you'll see it filed under lsm_job_s...volume_get(3) in the man pages, that's just the truncated name being cute about it πΈ). It's a C function, it's about jobs, and it hands you back a volume when everything's done. Let's go π«Ά
π NAME π
lsm_job_status_volume_get β check on the status of a job with lsm_volume returned.
Like, the whole point: you got a job, you wanna know how it's doing, and when it's finished you get the volume back. main character behaviour fr fr π
β¨ SYNOPSIS β¨
int lsm_job_status_volume_get (lsm_connect *conn, const char *job_id,
lsm_job_status *status, uint8_t *percent_complete, lsm_volume **vol,
lsm_flag flags);
look at that signature. six arguments. she's thorough π
π ARGUMENTS π
connβ a valid connection pointer. Has to actually be a validlsm_connectpointer, no faking the vibe check bestie.job_idβ a string. This is the job you're checking the status on. Which job? That job. πstatusβ output pointer oflsm_job_status. The possible values are:LSM_JOB_COMPLETEβ job complete with no error. slay, we ate β¨LSM_JOB_ERRORβ job complete with error. π not the vibe.LSM_JOB_INPROGRESSβ job is still in progress. hold on, she's working π
percent_completeβ output pointer ofuint8_t. The percent the job is complete. Domain is0..100. So like, zero to one hundred, no funny business.volβ output pointer oflsm_volumefor the completed operation. > heads up bestie: the returned value needs to be freed with a call tolsm_volume_record_free. Don't just leave her hanging, free her π«Άflagsβ reserved for future use, must beLSM_CLIENT_FLAG_RSVD. That's it, that's the only allowed value, periodt.
π VERSION π
1.0
πΈ DESCRIPTION πΈ
Check on the status of a job and it returns the volume information when complete. That's literally the whole plot. You ask, it tells you where the job's at, and when it's done you get your lsm_volume back. iconic behaviour honestly π
β RETURN β
Error code as enumerated by lsm_error_number. The possibilities, in all their glory:
LSM_ERR_OKβ on success. we love to see it π₯LSM_ERR_INVALID_ARGUMENTβ when any argument isNULLor not a validlsm_connectpointer or invalid flags. basically you gave her something she can't work with πLSM_ERR_NOT_FOUND_JOBβ when job not found. the job? gone. not in the group chat. π
and that's the whole page bestie, no cap, every flag and every error code accounted for π§
signing off: this was lsm_job_status_volume_get, from the lsm_job_s...volume_get(3) page, dated February 2026 β mwah, go free your volumes πβ¨
π¦ 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