Skip to main content
NetApp Knowledge Base

Slow CIFS/SMB File Access on FlexCache Volumes

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • SMB/CIFS protocol
  • FlexCache
  • FSx

Issue

  • Users experience significant delays (1.5–2 minutes or more) when opening or saving files (e.g., 30–150 MB Excel/spreadsheet documents) on CIFS/SMB shares hosted on FlexCache volumes. Expected file open time is under 30 seconds. The issue impacts hundreds of concurrent users and is production-affecting.
  • File open times: 1.5–2 minutes for 30–50 MB files (expected: <30 seconds)
  • FlexCache misses and high fc_retrieve_latency (hundreds of ms to seconds)
  • CSM session op latency (spinnp_op_latency): >500 ms, often several seconds
  • CSM session defer queue events incrementing heavily
  • Elevated TCP retransmissions and out-of-order packets on intercluster network path
  • Workload Dblade Delay Center (Cache Node):
start                       end                         instance                       iops read  iops write  iops other  total_ops  total_latency read (us)  delay_flexcache_ral_wait_time(us)  delay_flexcache_spinhi_wait_time(us)  delay_wafl_susp_other_wait_time(us)
2026-05-05 08:50:44+00:00  2026-05-05 08:51:44+00:00  vol_Share__0001-wid26319        0.38       0.13        16.33       16.85      90,467                    10,597                             2,336                                 10,560
2026-05-05 09:00:44+00:00  2026-05-05 09:01:44+00:00  vol_Share__0001-wid26319        0.32       0.03        15.80       16.15      3,104,229                 159,550                            1,366                                 146,408
2026-05-05 09:08:44+00:00  2026-05-05 09:09:44+00:00  vol_Share__0001-wid26319        0.17       0.07        17.65       17.88      9,346,544                 472,873                            11,777                                477,391
  • FlexCache Retrieve Latency (waflremote — Cache Node):
start                       end                         instance  fc_retrieve_ops  fc_retrieve_latency (us)
2026-05-05 08:49:44+00:00  2026-05-05 08:54:44+00:00  0          4,473            133,314
2026-05-05 08:59:44+00:00  2026-05-05 09:04:44+00:00  0          8,939            1,807,009
2026-05-05 09:04:44+00:00  2026-05-05 09:09:44+00:00  0          5,863            3,155,572
2026-05-05 09:14:44+00:00  2026-05-05 09:19:44+00:00  0          8,209            4,982,795
2026-05-05 09:39:44+00:00  2026-05-05 09:44:44+00:00  0          5,919            8,016,603
  • CSM Session Latency (Cache Node — spinnp_op_latency vs. service latency):
start                       end                         instance            spinnp_op_latency (us)  spinnp_req_service_latency (us)
2026-05-05 08:55:01+00:00  2026-05-05 08:59:44+00:00  0x11064f358fa23cf7     125,624                 1,338
2026-05-05 09:05:01+00:00  2026-05-05 09:09:44+00:00  0x11064f358fa23cf7     3,946,479               114,412
2026-05-05 09:15:01+00:00  2026-05-05 09:19:44+00:00  0x11064f358fa23cf7     5,458,466               1,292,253
2026-05-05 09:40:01+00:00  2026-05-05 09:44:44+00:00  0x11064f358fa23cf7     9,194,737               2,372,408
  • Origin Retrieve Message Latency (confirming origin is healthy):
start                       end                         instance  fc_retrieve_message_latency (us)  fc_retrieve_message_ops
2026-06-16 06:45:26+00:00  2026-06-16 06:50:26+00:00  0          2,081                             27,978
2026-06-16 07:05:26+00:00  2026-06-16 07:10:26+00:00  0          2,294                             20,678
2026-06-16 07:15:26+00:00  2026-06-16 07:20:26+00:00  0          1,483                             42,286
  • remote set Output (Cache Node):
Node: cache-node-01
Autoscrub:                 on
Cancel FC Ops:             on
Directory chunk loading:   enabled
Expansive:                 off
Fastpath:                  on
Logical directory caching: logical
Reclaim:                   on
Trace:                     on
bli-decrement: 1
bli-increment: 2
bli-threshold: 0
block-invalidate-test: off
blocks-prefetch-factor: 4
bulkattr-cache-size-limit: 32 MB
cache-all: 3000000
cache-rw: 512
dp-cache-all: 100000
csm-min-connections: 65535
fc-disconnect-expiry: 3600
fc-disconnect-timeout: 120
fc-min-free: 10
filemap-cache-entries-limit: 1608808
filemap-cache-low-water-mark-pcnt: 80
flexcache-writeback-origin-minfree-percent: 20
inode-alloc-limit: 32
lookup-cache-entries-limit: 313632        <<< Key indicator — oversubscribed for millions of files
negative-lookup-cache: on
origin-protection: on
origin-protection-size-limit: 500
parallel-retrieval-limit: 128
prioritize-retrieve-sleepers: on
retrieve-block-limit: 64
scrub-max-async: 512
scrub-in-stripe: on
sideload: on
streams-caching: on
stripe: on
use-incore-atime: on
ral-objects-freelist-size:
   Data Buffers Freelist: current 256 max 0
   Retrieve Freelist: max 256
   RetrieveClient Freelist: max 256

Note : CSM connection starvation: CSM allocates medium-priority TCP connections proportional to the origin's CPU count. Example: A 4-CPU origin gets only 4 connections (2 request + 2 response). All remote I/O funnels through these limited connections, causing head-of-line blocking and defer queue buildup when requests arrive faster than connections can process them.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.