Evan Martin (evan) wrote in evan_tech,
Evan Martin

tracking down nfs stats

tcpdump on my machine indicates:
09:09:03.835014 IP mouse.2280902084 > trout.nfs: 144 fsstat [|nfs]
09:09:03.835208 IP trout.nfs > mouse.2280902084: reply ok 168 fsstat [|nfs]
09:09:04.331178 IP mouse.4224086465 > trout.nfs: 144 fsstat [|nfs]
09:09:04.331382 IP trout.nfs > mouse.4224086465: reply ok 168 fsstat [|nfs]

and so on approximately every 0.5 sec. How do I track down what process is doing this?
I have some guesses, but is there a more principled way of going about it than killing things one by one?

Oh wait, lsof -N does it, I think? Ok, then, how do I track down what’s causing a process to respawn? ps axf indicates it has no parent which means it just daemon()‘d?

  • blog moved

    As described elsewhere, I've quit LiveJournal. If you're interested in my continuing posts, you should look at one of these (each contains feed…

  • dremel

    They published a paper on Dremel, my favorite previously-unpublished tool from the Google toolchest. Greg Linden discusses it: "[...] it is capable…

  • treemaps

    I finally wrote up my recent adventures in treemapping, complete with nifty clickable visualizations.

  • Post a new comment


    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.