lsm_job_status_ss_get(3)

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

πŸ’– lsm_job_status_ss_get β€” bestie edition πŸ’–

okay so this one lives in the Libstoragemgmt C API Manual, and it's literally your go-to for checking on a job and grabbing the snapshot set it made. very "are we there yet" but make it ✨infrastructure✨


🌸 NAME 🌸

lsm_job_status_ss_get β€” check on the status of a job with lsm_fs_ss returned.

like. the whole point. the assignment, if you will. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int lsm_job_status_ss_get (lsm_connect *conn, const char *job,
       lsm_job_status *status, uint8_t *percent_complete, lsm_fs_ss **ss,
       lsm_flag flags);

πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a valid connection pointer, bestie. no fake ones, no NULLs, we check.
  • job β€” a string. it's the job id you wanna check on. the little name tag of the task.
  • status β€” output pointer of lsm_job_status. the possible values are, and I quote, a whole vibe:
    • LSM_JOB_COMPLETE β€” job complete with no error. ate and left no crumbs. πŸ‘‘
    • LSM_JOB_ERROR β€” job complete with error. πŸ’€ it tried.
    • LSM_JOB_INPROGRESS β€” job is still in progress. it's giving "loading…" energy, be patient.
  • percent_complete β€” output pointer of uint8_t. percent job complete, domain 0..100. so like, how done are we. very main-character-progress-bar.
  • ss β€” output pointer of lsm_fs_ss for the completed operation. and listen: the returned value must be freed with a call to lsm_fs_ss_record_free. do not ghost it. it will leak and you will be sad. 🫢
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. don't get creative, the future hasn't happened yet. πŸ™ˆ

⭐ VERSION ⭐

1.0 β€” the classic. iconic. no notes.


πŸ’œ DESCRIPTION πŸ’œ

Check on the status of a job and return the snapshot information when it's complete. that's it, that's the whole thing. you ask "hey how's that job doing", and when it's done it hands you the snapshot info too. two birds, one extremely efficient system call. 🌈


πŸ”₯ RETURN πŸ”₯

Error code as enumerated by lsm_error_number. the lineup:

  • LSM_ERR_OK β€” on success. slay. ✨
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL, or not a valid lsm_connect pointer, or the flags are invalid. basically "girl what did you pass me". 😭
  • LSM_ERR_NOT_FOUND_JOB β€” when the job is not found. it's not here. it never was. move on. πŸ’€

heads up bestie: ss is an output pointer, so if you don't call lsm_fs_ss_record_free on what comes back, that memory is just out there, unattended, in the wild. free it. for me. πŸ₯Ί

that's the whole page fr fr β€” written up in the Libstoragemgmt C API Manual, version lsm_job_status_ss_get(3), dated February 2026. mwah. go forth and check your jobs, queen. πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from