lsm_job_status_get(3)

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

✨ lsm_job_status_get ✨

okay bestie, so we're in the Libstoragemgmt C API Manual and today's main character is lsm_job_status_get(3) πŸ’… she's the one you call when you just wanna know how's my job doing without asking for a whole data dump back. lowkey the chillest little function in the whole library.


🌸 NAME 🌸

lsm_job_status_get β€” check on the status of a job with no data returned.

like... just vibes and a status, no receipts 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int lsm_job_status_get (lsm_connect *conn, const char *job_id,
lsm_job_status *status, uint8_t *percent_complete, lsm_flag flags);

πŸ’– ARGUMENTS πŸ’–

  • conn β€” a valid connection, bestie. gotta be legit or she's not talking to you.
  • job_id β€” a String. it's the job id, iykyk. the little name tag your job's been wearing this whole time.
  • status β€” output pointer of lsm_job_status. she writes the answer here. the possible values are literally:
    • LSM_JOB_COMPLETE β€” job complete, no error. we ate and left no crumbs ✨
    • LSM_JOB_ERROR β€” job complete but with an error. not the vibe 😭
    • LSM_JOB_INPROGRESS β€” job is still in progress. she's cooking, give her a minute πŸ“
  • percent_complete β€” output pointer of uint8_t. percent job complete. domain 0..100, so don't come at her with 137, she will not know what to do with that.
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. like, that's the only accepted value, periodt.

🌈 VERSION 🌈

1.0 β€” she's been iconic since day one, no cap.


πŸ¦‹ DESCRIPTION πŸ¦‹

Check on the status of a job β€” no data, or just ignore the data that comes back on completion. that's it. that's the whole function. you want the status, not the whole story, and honestly? respect 🫢


⭐ RETURN ⭐

error code as enumerated by lsm_error_number. the way this function hands you a whole enum instead of just being normal πŸ’€ here's the rundown:

  • LSM_ERR_OK β€” on success. slay.
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL, or it's not a valid lsm_connect pointer, or the flags are invalid. basically she clocked you πŸ‘‘
  • LSM_ERR_NOT_FOUND_JOB β€” when the job is not found. that job is gone gone πŸ™ˆ

ngl, if job_id doesn't exist you're getting LSM_ERR_NOT_FOUND_JOB and there's no cute workaround, that's just the truth fr fr.

kisses, and good luck out there with your jobs πŸ’œ β€” this was the Libstoragemgmt C API Manual, page lsm_job_status_get(3), in the lsm_job_status_get edition, dated February 2026. mwah, go check on your jobs bestie πŸ§šπŸ’–

πŸ“¦ where this page comes from