CIFS Error: Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree

GRIMSTONER — Wed, 04 Jun 2025 20:58:16 GMT

I've recently started getting these errors:

Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree: clientIP:port 192.168.1.51:57914, directory "<directory>" on share "<CIFS share>".

In here: https://library.netapp.com/ecmdocs/ECMP12452955/html/vserver/cifs/options/show.html

You can set -max-watches-set-per-tree... what is the effect of changing this?

Re: CIFS Error: Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree

markcrouch — Wed, 27 Jul 2016 02:54:18 GMT

We were seeing this in our environment too - and it was actually taking down IIS servers that were serving content from the NetApp CIFS share. I raised a support ticket and they pointed me to the following article, which basically says in 8.3.1 they introduced the ability to manage previously hard-coded thresholds for CIFS/SMB related session parameters:

https://library.netapp.com/ecmdocs/ECMLP2348067/html/GUID-48836784-E9AB-443C-BE01-4BF1E9F7F2E5.html

The default of 100 was not high enough in our environment for max-watches-set-per-tree. We set this to 500 (max value is 4294967295 as per the man page). I've confirmed with NetApp and during implementation the change is non-disruptive to existing CIFS sessions. You do need to execute the command from advanced priv mode.

We're still waiting to validate it's fixed our issue, though I'm highly confident as the issue started immediately after our upgrade to 8.3.1, after 2 years of otherwise stability.

topic CIFS Error: Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree in ONTAP Discussions

CIFS Error: Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree

Re: CIFS Error: Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree