PROBE::NFS.PROC.(3stap)

💅 PROBE::NFS.PROC.COMMIT_DONE 💅

okay bestie, welcome to the Network File Storage Tapsets corner of the SystemTap Tapset Reference (section 3stap) 🎀 this little page is all about one specific probe — probe::nfs.proc.commit_done — and no cap, it's the one that catches the NFS client being like "ok got ur reply, mwah" 🫶

---

✨ NAME ✨

probe::nfs.proc.commit_done</purl> — NFS client response to a commit RPC task

Like, literally: the client's reaction when the commit RPC task comes back. That's the whole vibe. 💖

---

✨ SYNOPSIS ✨

probe nfs.proc.commit_done {}

that's it. no args, no fuss, just a little empty {} waiting for the moment. iconic behavior, honestly. ✨

---

✨ VALUES ✨

these are the juicy lil fields you get to peek at inside the probe, and bestie you're gonna want all of them:

• status — result of last operation
• prot — transfer protocol
• version — NFS version
• timestamp — V4 timestamp, which is used for lease renewal
• count — number of bytes committed
• valid — fattr->valid, indicates which fields are valid
• server_ip — IP address of server

like, seven whole values?? we ate. 🍓

---

✨ DESCRIPTION ✨

Fires when a reply to a commit RPC task is received or when some commit operation error occur (timeout or socket shutdown). 😭

so basically: it's the "did it land or did it flop" probe. either the reply came home 🏠 or something went wrong and it's giving timeout or socket shutdown energy. either way, this probe is the one who tells you. main character energy fr fr. 👑

---

✨ SEE ALSO ✨

• tapset::nfs_proc(3stap) — go read ur sister page, she knows things 🦋

---

SystemTap Tapset Reference • Version: September 2026 — ok that's the whole page bestie, ty for reading, go probe something slay ✨💖🧚