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

✨ probe::nfs.fop.write — NFS client write operation ✨

okay bestie, welcome to the Network File Storage Tapsets section of the SystemTap Tapset Reference 💖 this is the page for probe::nfs.fop.write, and it's a short one but it's got lore, so let's get into it 🫶

---

🌸 NAME 🌸

probe::nfs.fop.write — NFS client write operation 💅

it's giving "the write operation, but for the NFS client". that's the whole vibe. periodt.

---

✨ SYNOPSIS ✨

probe nfs.fop.write {}

that's it. no args, no params, no little arguments to babysit. she takes nothing and she runs. iconic honestly 🎀

---

🦋 VALUES 🦋

• devname — the block device name 🌈 that's the one (1) value this probe hands you, and it's literally just the name of the block device. no cap.

---

💜 DESCRIPTION 💜

okay so here's the tea, and it's important tea ☕

SystemTap implements this probe using the vfs.do_sync_write probe. Which means — and this is the part you gotta hold onto — it will also pick up operations other than the NFS client write operations. 🫠

like. she's not exclusive. she's showing up for the NFS client writes and for other stuff too, because that's just how the vfs.do_sync_write implementation works. so if you're out here expecting this probe to be strictly NFS-client-write-only, bestie, it is not, and now you know before you get humbled by your own trace output 😭

⚠️ real talk: the description is literally a caveat. nfs.fop.write is built on top of vfs.do_sync_write, so extra non-NFS-write operations can come through. don't @ me, @ the implementation.

---

👑 SEE ALSO 👑

• tapset::nfs(3stap) — go read the NFS tapset page, it's the main character of this whole friend group 💖

---

💖 a little sign-off 💖

this lil page comes from the SystemTap Tapset Reference, and the version/date situation on the footer is September 2026 🌸 so that's the era we're living in. go forth, probe responsibly, and remember: devname, vfs.do_sync_write, and the fact that she's not exclusive 💅✨🦋