lsm_job_status_fs_get(3)

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

πŸ’– lsm_job_status_fs_get β€” the Libstoragemgmt C API Manual's iconic lil' job-checker πŸ’–

okay bestie, gather round, because this one is the lsm_job_status_fs_get(3) page and she is serving πŸ’…


✨ NAME ✨

lsm_job_status_fs_get β€” check on the status of a job with lsm_fs returned. yep that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

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

look at her go 😭 six whole parameters, main character energy fr fr


πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a valid connection pointer. like, it has to actually be valid bestie, don't be out here passing nonsense πŸ’€
  • job_id β€” a String. the job you wanna check on πŸ‘€
  • status β€” output pointer of lsm_job_status. the possible values are, and I quote the vibes exactly:
    • LSM_JOB_COMPLETE β€” job complete with no error. ate and left no crumbs ✨
    • LSM_JOB_ERROR β€” job complete with error. not the slay we wanted 😭
    • LSM_JOB_INPROGRESS β€” job is still in progress. she's working on it, be patient πŸ’œ
  • percent_complete β€” output pointer of uint8_t. percent job complete. domain is 0..100, so like, don't come at me with 200, that's not the assignment πŸ“
  • fs β€” output pointer of lsm_fs for the completed operation. the returned value must be freed with a call to lsm_fs_record_free. yes literally, you gotta clean up after yourself, no leaving crumbs 🧚
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. that's it, that's the whole rule, no improvising πŸ”₯

⭐ VERSION ⭐

1.0 β€” she's a classic, an icon, a legend πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

check on the status of a job and return the fs information when complete. that's the tea β˜• short, sweet, does exactly what it says on the tin, periodt πŸ’…


πŸ’€ RETURN πŸ’€

error code as enumerated by 'lsm_error_number'. the lineup:

  • 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. so like, if you passed garbage, that's on you bestie πŸ™ˆ
  • LSM_ERR_NOT_FOUND_JOB β€” when job not found. she's not here, she's booked and busy somewhere else 😭

anyway, that's the whole page. go forth and check those jobs, and remember: free your fs with lsm_fs_record_free, because leaving memory hanging is not the vibe 🫢

smooches and this came from the Libstoragemgmt C API Manual, dated February 2026 β€” lsm_job_status_fs_get, version 1.0, forever iconic, no cap πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from