PROBE::SCSI.IOCOMP(3stap)

💖 PROBE::SCSI.IOCOMP 💖

okay bestie, gather round — this is a page from the SCSI Tapset of the SystemTap Tapset Reference, and it's literally all about one probe. Let's get into it. 🦋

---

✨ NAME ✨

probe::scsi.iocompleted — SCSI mid-layer running the completion processing for block device I/O requests 🎀

No cap, that's the whole vibe: this probe fires when the SCSI mid-layer is doing the completion part of block device I/O. It's giving "the request is done, let's wrap it up" energy. 💅

---

🌸 SYNOPSIS 🌸

probe scsi.iocompleted {}

That's it. That's the whole thing. One line, zero arguments, maximum main character. 👑

---

👑 VALUES 👑

These are all the values you can peek at inside this probe. Every single one, we're not skipping a single one, periodt. 💜

• data_direction — tells you whether this command is going from the device or to the device. Direction check, fr fr. 🧭
• req_addr — the current struct request pointer, handed to you as a number. 🫶
• data_direction_str — same data direction as above, but as a string this time. ✨
• device_state — the current state of the device. 🌈
• device_state_str — the current state of the device, but as a string. 🍓
• goodbytes — the bytes completed. The good ones. 😌
• lun — the lun number. 🔥
• channel — the channel number. 📡
• dev_id — the scsi device id. 🏷️
• host_no — the host number. 🏠

not me listing all ten values because every single one matters 💀 — yes, data_direction and data_direction_str are both there, and yes, device_state and device_state_str are both there. One's the raw thing, one's the string version. That's just how it is, bestie. 🙈

---

🦋 SEE ALSO 🦋

• tapset::scsi(3stap) — go read this one too, iykyk 💖

---

and that's the whole page, no crumbs left 🧚

This was the SystemTap Tapset Reference, September 2026 edition. mwah, slay, bye bestie 💅✨