Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a linux file server running CentOS 6. Files are accessed via NFS4.

Sometimes I have problems with disk io load. I want to find out what is causing them.

I can find out which client is causing them with tcpdump and nfsiostat (on the clients). But I want to know either which files are accessed or which process is doing the accesses. Then I can think about a solution for it.

I have tried to use wireshark to decode the accesses, but it is hard to read when open and read/write are not close together or you have lots of files with similar names (directories are not shown, just dir handles). If you have a lot of activity it would be nice to have a way to sort files by activity to find out what is the culprit.

Does anybody know of a solution for this?

share|improve this question
Do you want to look on the client or the server? – womble Jul 23 '12 at 1:06

You can use either lsof or ftop (the last one is on EPEL repo)

For example:

lsof -N /mnt/nfs/*


share|improve this answer

A good start is to use/install iotop, i find it very handy for similar problems.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.