Skip to main content
NetApp Knowledge Base

Cloud sync fails to copy files with trailing blank spaces (' ') and/or dots ('.') for CIFS long names

Views:
239
Visibility:
Public
Votes:
2
Category:
cloud-sync
Specialty:
nas
Last Updated:

Applies to

  • Cloud sync
  • ONTAP 9
  • ONTAP SMB Target

Issue

  • For SMB Target , Cloud sync fails to copy files with trailing blank spaces (' ') and/or dots ('.') for CIFS long names 
  • Cloud sync shows copy failure reason as "ENOENT: no such file or directory"
clipboard_ecc0b1364030ea4297a9ab851da4327bf.png
 
  • Failed logs:
    • Data broker Failed logs indicates that cloud sync created a temporary file starting with ('.') and then attempted to rename the file to original file with trailing spaces and/or dots at the end 
    • This rename operation fails with error "ENOENT: no such file or directory"

[2021-09-29T18:16:09.184] [INFO] [TRANSFERRER] [1] [13473] [614af5db716b8e33fcf50c66] [COPY] FAILED: source { nfs: { host: '10.216.41.102', export: '/test_vol1', version: '3', path: 'new1', provider: 'nfs' } } target: { cifs: { host: '10.216.41.102', share: '/ntfs_vol', version: '2.1', provider: 'cifs' } } entry: { path: 'file_with_dot.', type: 'FILE', size: 0, mode: 33188, uid: 0, gid: 0, mtimeSec: 1632919545, tempEntryName: '.file_with_dot._mdd7F6n_netapp' } [Error: ENOENT: no such file or directory, rename 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/.file_with_dot._mdd7F6n_netapp' -> 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/file_with_dot.'] { errno: -2, code: 'ENOENT', syscall: 'rename', path: 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/.file_with_dot._mdd7F6n_netapp', dest: 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/file_with_dot.' }

[2021-09-29T18:16:09.184] [INFO] [TRANSFERRER] [1] [13473] [614af5db716b8e33fcf50c66] [COPY] FAILED: source { nfs: { host: '10.216.41.102', export: '/test_vol1', version: '3', path: 'new1', provider: 'nfs' } } target: { cifs: { host: '10.216.41.102', share: '/ntfs_vol', version: '2.1', provider: 'cifs' } } entry: { path: 'file_with_space ', type: 'FILE', size: 0, mode: 33188, uid: 0, gid: 0, mtimeSec: 1632919531, tempEntryName: '.file_with_space _RHHW0FJ_netapp' } [Error: ENOENT: no such file or directory, rename 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/.file_with_space _RHHW0FJ_netapp' -> 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/file_with_space '] { errno: -2, code: 'ENOENT', syscall: 'rename', path: 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/.file_with_space _RHHW0FJ_netapp', dest: 'mnt/614af5db716b8e33fcf50c66/03bce881-4a19-4e0f-89f7-5142e508158d_trg/file_with_space ' }

 
  • Packet Traces:
    • Packet Traces show the temporary file creation was successful but when cloud sync attempted to rename it to original file, it fails with error  Error: STATUS_OBJECT_NAME_INVALID
614    2021-09-29 18:16:09    10.216.41.22    10.216.41.102 SMB2 SetInfo Request FILE_INFO/SMB2_FILE_RENAME_INFO File: .file_with_dot._mdd7F6n_netapp NewName:file_with_dot.
615    2021-09-29 18:16:09    10.216.41.102    10.216.41.22 SMB2 SetInfo Response, Error: STATUS_OBJECT_NAME_INVALID
                                                             
622    2021-09-29 18:16:09    10.216.41.22    10.216.41.102 SMB2 SetInfo Request FILE_INFO/SMB2_FILE_RENAME_INFO File: .file_with_space _RHHW0FJ_netapp NewName:file_with_space 
623    2021-09-29 18:16:09    10.216.41.102    10.216.41.22 SMB2 SetInfo Response, Error: STATUS_OBJECT_NAME_INVALID

 

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.