[gregw2]

This. (Combine with sudo too!)

Now if I could just track NFS client traffic on a client associated with a PID (without having NFS server access). All I can get is all-PID/client-kernel data info vi nfsstat, nothing tying to a PID, filename, directory or inode to tell me which PID is causing all the NFS traffic!

[fragmede]

    iotop?

[gregw2]

Tried it, I think the problem is the nfs io comes from the kernel and is not tied to a PID?