PROBE::NFS.PROC.(3stap)

📦
version 5.6 · 9 versions
, in centos-stream 10, centos-stream 9, fedora 43, fedora 44

💖 PROBE::NFS.PROC.(3stap) 💖

okay bestie, welcome to the Network File Storage Tapsets manual — this one's all about that one specific little probe and it's lowkey iconic 🦋

✨ NAME ✨

probe::nfs.proc.write_done — it's the NFS client's lil "we got a reply!!" moment for a write RPC task 💅

🌸 SYNOPSIS 🌸

probe nfs.proc.write_done {}

no args, no drama, just vibes 🎀

🫶 VALUES 🫶

these are the goodies you get to peek at when the probe fires. obsessed honestly.

  • server_ip — the IP address of the server, aka who we're talking to 🌐
  • valid — this is fattr->valid, and it literally tells you which fields are valid. a vibe check for struct fields, fr fr ✨
  • status — the result of the last operation. did it slay or did it flop? this is where you find out 👑
  • prot — the transfer protocol. the how of the whole thing 🌈
  • version — the NFS version 🧚
  • timestamp — a V4 timestamp, which is used for lease renewal. very "keeping the lease alive, no cap" energy ⭐
  • count — number of bytes written. the receipts 📝

💜 DESCRIPTION 💜

So here's the tea: this probe fires when a reply to a write RPC task is received — OR when some write error occurs (think timeout, or a socket shutdown 😭).

like... it's giving "the write finished, one way or another". either it came back happy or it came back messy, and either way this probe is gonna tell you about it 💀

🔥 SEE ALSO 🔥

that's the whole page, bestie, you ate that 🍓 go forth and trace responsibly 💖

SystemTap Tapset Reference — Version (blank, mysterious, main character energy) — September 2026 🎀

📦 where this page comes from