Skip to main content
NetApp Knowledge Base

SMB Rename of large zip files may fail with internal error due to VSCAN timeout

  1. Last updated
  2. Save as PDF
Views:
304
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP 9
  • Vscan (on-access)
  • Windows
  • CIFS/SMB

Issue

  • With on-access Vscan enabled, a client fails an SMB rename operation with internal error
  • Increased latency for the affected SVM and share may be observed
  • Mandatory Scan is disabled
  • The SMB rename operation (SMB2_COM_SET_INFO) fails on CIFS operation time out as per EMS / event log show entry:
Nblade.CifsOperationTimedOut: Detected a timed out CIFS operation.
SMB command for this operation: SMB2_COM_SET_INFO,
Number of times this command was suspended: 6,
Number of times this command was restarted: 0,
Last CSM error during this operation: CSM_OK,
Remote blade UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (cluster01n01),
Is QoS enabled: QoS_disabled,
Last SpinNp error during this operation: SPINNP_ERR_OFFBOX_VSCAN_REQD, Client IP address: xxx.xxx.xxx.xxx, Local IP address: xxx.xxx.xxx.xxx,
Target Vserver ID: 12, Target disk's DSID: 1234
 

  • Packet trace shows STATUS_INTERNAL_ERROR

SetInfo Response, Error: STATUS_INTERNAL_ERROR

 

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.