The long and short seems to be - I'm getting low_mbuf CPs on the filter head, and at the time the error message occurs - I'm also getting back to back CPs. So have a reboot pending, and probably a code update in the near future.
On 15 February 2016 at 13:32, tmac tmacmd@gmail.com wrote:
Are you hosting your datastores on SATA drives? I have seen this before (many times) when customer use SATA and try to host too many virtual machines and they do not turn on the Storage I/O control. (premium feature!).
Turning on SIO control does not always solve this either.
--tmac
*Tim McCarthy* *Principal Consultant*
On Mon, Feb 15, 2016 at 7:42 AM, Basil basilberntsen@gmail.com wrote:
That's a very generic warning- I'd open a case.
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
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters