PROBE::IOSCHEDULER_TRACE.ELV_ABORT_REQUEST(3stap)

✨ NAME ✨

probe::ioscheduler_trace.elv_abort_request β€” ok bestie, this probe fires when a request is aborted πŸ’… it lives in the IO Scheduler and block IO Taps chapter of the SystemTap tapset reference, and it is so niche and so useful.


πŸŽ€ SYNOPSIS πŸŽ€

probe ioscheduler_trace.elv_abort_request {}

That's it. No args, no drama. She just sits there and waits for a request to get aborted, then she tells you everything πŸ‘‘


πŸ’– VALUES πŸ’–

Every one of these is a lil variable you get to peek at inside your probe handler. Collect them like PokΓ©mon πŸ¦‹

  • rq β€” the address of the request. That's the actual request object, the main character of this whole situation.
  • disk_major β€” the disk major number of the request. Yes, numbers have majors. Slay.
  • elevator_name β€” the type of I/O elevator that's currently enabled. The elevator is the scheduler, and she has a name πŸ’…
  • disk_minor β€” the disk minor number of the request. The little sibling of disk_major, no cap.
  • rq_flags β€” the request flags. Little bits of metadata that say stuff about the request.
  • name β€” the name of the probe point. It's giving "who am I", and the answer is literally the probe point's name.
ngl if you're debugging why requests keep getting aborted, rq_flags, elevator_name, disk_major and disk_minor are your besties here. Grab rq if you want to go deeper. 🫢

🌈 SEE ALSO 🌈


SystemTap Tapset Reference Β· Ver Β· September 2026 πŸŽ€

kk that's the whole page, thanks for coming to my ted talk, go abort some requests (responsibly) πŸ’–βœ¨πŸŒΈ

πŸ“¦ where this page comes from