Find out the configuration with which the nfs client is connected to the nfs server.
Bouncing my head to my keyboard while trying to find out where is the bottleneck on an nfs client-server relationship, I found out how to see the configuration with which the nfs client is connect to the server:
And the output is:
/nfsshare from nexenta.nfs-servers.example.com:/volumes/datastore/dataset/ Flags: rw,relatime,vers=4,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.0.2.21,minorversion=0,local_lock=none,addr=10.0.2.245
Knowing exactly how the client is connected to the server, you can find more easily where the problem is.
Using the nfsstat -m command, you get the information about all nfs mounts. The -m switch is present on centOS, but abscent on FreeBSD, in which I do also performance tests.
You can also find all this information and also all the information about all mounts ( not only nfs mounts) if you execute:
I am trying to get this info on FreeBSD, if everyone knows everything about this, please post a comment. I also asked a question at http://unix.stackexchange.com/questions/91594/nfs-mount-properties-options-in-freebsd to help me find the solution.