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

πŸ’… PROBE::NFS.AOP.W β€” it's giving "NFS client just finished writing data"

okay bestie so this is a page straight out of the Network File Storage Tapsets, and it lives in section 3stap of your SystemTap manual. It's all about one lil probe and the absolute pile of values it hands you. Let's get into it 🫢


✨ NAME ✨

probe::nfs.aop.write_end β€” NFS client complete writing data

Like. That's the whole vibe. The NFS client is done writing. Periodt. πŸ’…


🌸 SYNOPSIS 🌸

probe nfs.aop.write_end {}

no arguments, no nothing, it just goes. main character energy fr fr ✨


πŸŽ€ VALUES πŸŽ€

okay so when this probe fires, it's handing you a whole goodie bag of variables. every single one, no skipping:

  • offset β€” the start address of this write operation. where the writing begins πŸ¦‹
  • to β€” the end address of this write operation. where the writing stops. that's it, that's the range πŸ“
  • dev β€” the device identifier. which device, bestie 🧚
  • __page β€” the address of the page. yes it has two underscores up front, that's not a typo, that's just how she is 😭
  • size β€” write bytes. how many bytes got written πŸ’œ
  • sb_flag β€” super block flags
  • ino β€” the inode number πŸ‘‘
  • i_size β€” file length in bytes. how big the file is πŸ’«
  • i_flag β€” file flags
  • page_index β€” offset within mapping; can be used as a page identifier and a position identifier in the page frame. lowkey doing two jobs at once, we love a multitasker ⭐

πŸ’– DESCRIPTION πŸ’–

so here's the tea:

This probe fires when do a write operation on nfs, often after prepare_write. 🫢

It's also described as: Update and possibly write a cached page of an NFS file.

That's it, that's the whole deal. You catch the moment, you read the values, you slay. πŸ’…βœ¨


🌈 SEE ALSO 🌈


SystemTap Tapset Reference, September 2026 β€” that's the version and date stamp on this page, mwah, thanks for coming to my ted talk, go forth and probe responsibly πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from