ceph_mdsc_wait_for_reset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ceph_mdsc_wait_for_reset β€” the kernel API manual, bestie edition

okay so real talk, this is the manpage for ceph_mdsc_wait_for_reset from the Kernel API Manual, and it is exactly what it says on the tin: you sit there and wait for a reset that's already in progress to finish. no cap. let's get into it πŸŽ€


✨ NAME ✨

ceph_mdsc_wait_for_reset β€” wait for an active reset to complete πŸ¦‹


🌸 SYNOPSIS 🌸

int ceph_mdsc_wait_for_reset (struct ceph_mds_client *mdsc );

🫢 ARGUMENTS 🫢

  • mdsc β€” the MDS client. that's it, that's the whole vibe πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

bestie, the return value is the whole personality here, so let's go one by one πŸ‘‘

  • Returns 0 if the reset completed successfully or if there was literally no reset active. slay, nothing to worry about πŸ’…
  • Returns -EAGAIN if the reset completed but it came back with an error β€” that's your cue, caller, go retry πŸ”
  • oh and important: the internal error (like -ENOMEM) is not propagated, because callers like open or flock have genuinely no way to act on work-function internals. like, what are they supposed to do with that? 😭 so the detailed error is available via debugfs reset/status and tracepoints instead β€” iykyk πŸ”
  • Returns -ETIMEDOUT if we timed out waiting. yeah. we waited too long. ⏰
  • Returns -ERESTARTSYS if we got interrupted by a signal. rude but okay πŸ™ˆ
fr fr, don't go looking for -ENOMEM in the return value β€” it lives in debugfs reset/status and tracepoints, not here. periodt.

⭐ SEE ALSO ⭐


and that's the page, bestie! 🧚 this little masterpiece lives in ./fs/ceph, it's dated October 2026, and it's filed under ceph_mdsc_wait_for_reset(9) in the Kernel API Manual. go forth and wait for your resets responsibly πŸ’œπŸŒˆ

πŸ“¦ where this page comes from