Well, if it’s caused by low_mbuf, those are memory buffers that can be cleared with a reboot.
However, the issue will likely resurface unless there is a fix for the memory buffer issue.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net]
On Behalf Of Tony Bar
Sent: Tuesday, February 16, 2016 11:12 AM
To: Edward Rolison
Cc: toasters@teaparty.net
Subject: Re: NwkThd_00:warning: NFS response to client was slow
Edward -
Good luck with your corrective plan, but if you're getting back to back CPs simply rebooting or patching (unless there's a specific patch that is recommended against this behavior) isn't going to do much to solve your problem. These errors
are almost always caused by having too few physical disks in the underlying aggregate, or a workload that is too aggressive for the aggregate hosting it -- so you're best off relocating the workload (Storage vMotion, volume move, SnapMirror/NDMP dump) or expanding
the aggregate. Another thing you might want to check on is the free space on the aggregate (> 90-95% utilization) since that can also cause problems where housekeeping tasks such as changed block reclamation do not have adequate free space to run.
Anyway, to reiterate -- good luck, but keep the above in mind when considering your options.
Thanks!
On Feb 16, 2016, at 8:03 AM, Edward Rolison <ed.rolison@gmail.com> wrote: