This is a complete stab in the dark, but a command you can try to run is mbstat. My guess is CIFS may have been starved from ontap doing what it does, or there is a bug for some sort of memory leak.
I have experienced something similar to this a long time ago with DOT 7.3x (but not with the error you noted). I would start losing ICMP to the filer, then it would just give up and panic.. Turned out I would monitor it via mbstat, and could predict how long the filer would stay up based on buffers free....
Again, just a stab in the dark. I would open a support case on it.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Ray Van Dolson Sent: Monday, February 04, 2013 9:40 PM To: toasters@teaparty.net Subject: NT_STATUS_NO_MEMORY
Anyone ever encountered this error when attempting to access a CIFS share on an ONTAP 8.0.x system? ("NT_STATUS_NO_MEMORY").
We encountered reports from users of intermittent failures to connect to CIFS shares. From Windows hosts, things would just time out. From Samba clients, the above NT_STATUS_NO_MEMORY error was the result.
The "fix" ended up being to restart the CIFS service on the system, but wondering what the true root cause here might be. I'm unsure how accurate the error returned by the Samba client is -- in any case there doesn't appear to be a way to query memory utilization on the NetApp.
Thanks, Ray _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters