PROBE::NFS.FOP.R(3stap)

💖 PROBE::NFS.FOP.R — the read probe, bestie 💖

okay so this is a page from Network File Storage Tapsets (that's the 3stap manual, section 3, the SystemTap girlies know 👑). Sit down, grab a strawberry 🍓, and let's talk about probe::nfs.fop.read because honestly? iconic.

---

✨ NAME ✨

probe::nfs.fop.read — the NFS client read operation. that's her. that's the whole vibe. 📖

---

🌸 SYNOPSIS 🌸

probe nfs.fop.read {}

no arguments, no drama, just vibes and an empty pair of curly braces 💅

---

🦋 VALUES 🦋

here's what you get handed when this probe fires, and there's exactly one of them:

• devname — the block device name 💾 like, literally the name of the block device. that's it, that's the value, she's simple and she's serving.

---

💀 DESCRIPTION 💀

okay so this is the part where it gets a little messy, no cap 😭

SystemTap implements this probe using the vfs.do_sync_read probe. which means — and I need you to hear me on this — it will get operations other than the NFS client read operations. 🚨

so yeah. the probe is called nfs.fop.read but it's lowkey not only NFS client reads. it's giving "name tag says one thing, personality says another." not a bug, just how it's built, and now you know fr fr 🫶

---

🌈 SEE ALSO 🌈

• tapset::nfs(3stap) — go read the whole tapset, bestie, it's the mothership 🧚

---

that's the page!! every flag-free, option-free, chaotic little detail included, exactly as the source said it. now go forth and trace some reads 💜

🌸 this has been your SystemTap Tapset Reference, Ver — September 2026 edition — mwah, go touch some kernel code 🌸