https://community.netapp.com/t5/Network-and-Storage-Protocols/Other-latency-issue/m-p/104010#M7705 <P>&nbsp;</P><P>We had a CIFS client outage recently as they were disconnected from the volume/cifs share and when we analyzed data from NMC we saw &nbsp;the excessive latency on te CIFS protocol (250 milliseconds, though prior to this there was a spike of 1500 milliseconds delay at around 1:30pm EST). IOPs were very low/stable and well within the PAM/disk capacity range but the latencies aren’t .This is a problem of identifying the root cause on this issue that the both write/read latency on the na01_customer_data volume are low but “other_latency figure”&nbsp; on the volume latency view on NMC &nbsp;is high (110 milli seconds) and NOT write/read latencies!!. &nbsp;It needs to be worked out what CIFS other_latency is and I can’t tell what volume/qtree or CIFS client is the root cause of them since they don’t have any high IOPS at this moment</P><P>Please let me know your thoughts</P><P>&nbsp;</P><P>Actually on NFS client which is accessing to the same volume also we have this error, as we have&nbsp;rblk_nor/s almost 6260.&nbsp;</P><P>&nbsp;</P> Thu, 05 Jun 2025 04:24:37 GMT KIIKANZAVANNA 2025-06-05T04:24:37Z https://community.netapp.com/t5/Network-and-Storage-Protocols/Other-latency-issue/m-p/104010#M7705 <P>&nbsp;</P><P>We had a CIFS client outage recently as they were disconnected from the volume/cifs share and when we analyzed data from NMC we saw &nbsp;the excessive latency on te CIFS protocol (250 milliseconds, though prior to this there was a spike of 1500 milliseconds delay at around 1:30pm EST). IOPs were very low/stable and well within the PAM/disk capacity range but the latencies aren’t .This is a problem of identifying the root cause on this issue that the both write/read latency on the na01_customer_data volume are low but “other_latency figure”&nbsp; on the volume latency view on NMC &nbsp;is high (110 milli seconds) and NOT write/read latencies!!. &nbsp;It needs to be worked out what CIFS other_latency is and I can’t tell what volume/qtree or CIFS client is the root cause of them since they don’t have any high IOPS at this moment</P><P>Please let me know your thoughts</P><P>&nbsp;</P><P>Actually on NFS client which is accessing to the same volume also we have this error, as we have&nbsp;rblk_nor/s almost 6260.&nbsp;</P><P>&nbsp;</P> Thu, 05 Jun 2025 04:24:37 GMT https://community.netapp.com/t5/Network-and-Storage-Protocols/Other-latency-issue/m-p/104010#M7705 KIIKANZAVANNA 2025-06-05T04:24:37Z