lsm_job_s...volume_get(3)

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

✨ 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 valid lsm_connect pointer, 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 of lsm_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 of uint8_t. The percent the job is complete. Domain is 0..100. So like, zero to one hundred, no funny business.
  • vol β€” output pointer of lsm_volume for the completed operation. > heads up bestie: the returned value needs to be freed with a call to lsm_volume_record_free. Don't just leave her hanging, free her 🫢
  • flags β€” reserved for future use, must be LSM_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 is NULL or not a valid lsm_connect pointer 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