What type and speed disks are you using for the VMware environment? If you're using 15k disks there are a couple things I would start with. Check the output of the following:
priv set diag statit -b (wait 10 seconds) statit -e
You'll get some good info about the disks in this output. What are the xfers (iops)?
Also check: sysstat -c 10 -x 10
What do you see in the "CP ty" column? If you see an upper or lower case "b", then you're hitting back to back CPs. Basically, this means that the controller has a problem keeping up with the incoming writes.
If any of the above comes back abnormal I would open a case for deeper investigation.
Also, that message you're seeing is giving you the volume fsid, 0x1234567. You can use the "vol read_fsid <vol-name>" command (priv set diag) to see the volume fsid's. You'd have to run it on each volume until you find the one that matches what you see in the message regarding the slow response.
On Mon, Feb 15, 2016 at 6:44 AM, Edward Rolison ed.rolison@gmail.com wrote:
NwkThd_00:warning]: NFS response to client xx.xx.xx.xx for volume 0x1234567 was slow, op was v3 write, 65 > 60 (in seconds)
I have a filer head, on which I'm hosting ESX datastores. I've had a couple of instances now of this error (or one rather similar).
It correlates with VMware getting upset and VMs going read only. But it doesn't actually give me any insight into what is going on.
Has anyone run into this, and can give some further insight as to what might be causing and where I can look?
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters