Skip to main content
NetApp Knowledge Base

XCP sync task gets stuck when file or foldernames with prefix "UNC" present at source

Views:
113
Visibility:
Public
Votes:
0
Category:
netapp-xcp
Specialty:
nas
Last Updated:

Applies to

XCP SMB

Issue

  • The XCP sync task is stuck without any progress for a long time
  • XCP log shows xcp.synchronizer error.
  • Error:
2023-10-12 09:19:03,932 - ERROR - xcp.synchronizer - failed to copy "ntap\abc\test\test": (1, 'ReadFile', 'Incorrect function.')
2023-10-12 09:19:06,696 - ERROR - xcp.synchronizer - failed to remove from target "ntap\abc\test\test": [Errno 13] The process cannot access the file because it is being used by another process:
2023-10-12 09:19:50,352 - WARNING - xcp.fs - error setting timestamps on "ntap\abc\test\test": errno (code: 32) The process cannot access the file because it is being used by another process.
  • Folder gets created as file by XCP in destination.
  • Packet trace shows a loop of SMB CREATE call to create folder under the file and the filer responding NT error: STATUS_OBJECT_PATH_NOT_FOUND (0xc000003a)
No      Time            Source   Destination Proto Info
306154  11:22:29.509384 10.x.x.x 10.x.x.x    SMB2  Create Request File: ntap\abc\test\test\ts01
306155  11:22:29.509474 10.x.x.x 10.x.x.x    SMB2  Create Response, Error: STATUS_OBJECT_PATH_NOT_FOUND

 

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.