Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4709 results
    • Files are deleted by delete on close and waiting for someone close the files but it is not shown on locks shows
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Files_are_deleted_by_Delete_on_close_and_weiting_for_someone_close_the_files_but_it_not_shown_by_locks_show
      Applies to ONTAP 9 Issue Files are deleted by Delete-on-Close, but files are still shown by CIFS accessing due to someone opening the file and never closing it Files can not be accessible ONTAP send b...Applies to ONTAP 9 Issue Files are deleted by Delete-on-Close, but files are still shown by CIFS accessing due to someone opening the file and never closing it Files can not be accessible ONTAP send back the NT_status error "STATUS_DELETE_PENDING" By the command vserver locks show, there are no locks showing who is opening & locking those files
    • Unable to access shares using SMB1
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_access_shares_using_SMB1
      Nblade.noSmbVerNegotiated: For Vserver "vserver", Data ONTAP(R) could not negotiate with the client "192.168.139.61" because it does not support any of the SMB protocol versions that the client sent i...Nblade.noSmbVerNegotiated: For Vserver "vserver", Data ONTAP(R) could not negotiate with the client "192.168.139.61" because it does not support any of the SMB protocol versions that the client sent in the list "<PC NETWORK PROGRAM 1.0;LANMAN1.0;Windows for Workgroups 3.1a;LM1.2X002;LANMAN2.1;NT LM 0.12>".​​​​​ The FlexCache volume is always a FlexGroup volume, and not a FlexVol volume, you can only have a FlexCache volume as the origin volume.
    • Does SMB sigining work in Workgroup mode?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Does_SMB_sigining_work_in_Workgroup_mode
      Applies to ONTAP 9 SMB2 and later Answer ONTAP always advertises signing capability and it will be available with both, domain users and local users Note: Local users are users which data is stored on...Applies to ONTAP 9 SMB2 and later Answer ONTAP always advertises signing capability and it will be available with both, domain users and local users Note: Local users are users which data is stored on the vserver cifs config Additional Information The -is-signing-required parameter in vserver security commands does not enable signing per se, but enables the requirement that the client signs its requests Example with the parameter disabled: Example with the parameter enabled:
    • Stall at the end of a file copy to a FlexCache in write-back mode with File Explorer
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stall_at_the_end_of_a_file_copy_to_a_FlexCache_in_write-back_mode_with_File_Explorer
      Applies to ONTAP 9 FlexCache Write-back mode Issue There is a stall in the file copy using File Explorer with "Time remaining" displaying "About 5 seconds" when the file has one or more alternate data...Applies to ONTAP 9 FlexCache Write-back mode Issue There is a stall in the file copy using File Explorer with "Time remaining" displaying "About 5 seconds" when the file has one or more alternate data streams (ADS)
    • Writing large files fail because ONTAP does not support large IO using SMBv1
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Writing_large_files_fail_because_ONTAP_does_not_support_large_IO_using_SMBv1
      Applies to ONTAP 9 and later SMBv1 Issue Error while copying file size above 61+KB from servers using SMB and getting below error: cp file.mdf /dir/dir2/outbound/path/dirpath/cp: closing `/dir/dir2/ou...Applies to ONTAP 9 and later SMBv1 Issue Error while copying file size above 61+KB from servers using SMB and getting below error: cp file.mdf /dir/dir2/outbound/path/dirpath/cp: closing `/dir/dir2/outbound/path/dirpath/file.mdf': Input/output error No issues while writing smaller files(>64KB) Clients using SMBv2 are able to write large files without any issues No errors reported in ems logs
    • nslookup command could not resolve vserver host name
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/nslookup_command_could_not_resolve_vserver_host_name
      Applies to ONTAP 9 Name Services Issue nslookup command could not resolve the vserver host name
    • Access to CIFS share failed due to snapmirror relationship stuck in Quiesced state
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Access_to_CIFS_share_failed_due_to_snapmirror_relationship_stuck_in_Quiesced_state
      CIFS/SMB clients cannot access CIFS shares and EMS log shows below message Mon Jan 18 16:36:03 GMT [Node-01: kernel: Nblade_cifsShrConnectFailed_1:error]: params: {'errorDescription': 'No such object'...CIFS/SMB clients cannot access CIFS shares and EMS log shows below message Mon Jan 18 16:36:03 GMT [Node-01: kernel: Nblade_cifsShrConnectFailed_1:error]: params: {'errorDescription': 'No such object', 'vserverName': 'SVM', 'serverIp': '10.10.10.1', 'vserverId': '3', 'errorCode': '2', 'shareName': 'test_share', 'clientIp': '10.10.10.51'} CIFS share configuration looks fine CIFS share path exists snapmirror show command reveals that the relationship status is Quiesced and Healthy is false
    • XCP copy fails with nfs3 error 5: I/O error
      https://kb.netapp.com/on-prem/ontap/da/XCP/XCP-KBs/XCP_copy_fails_with_nfs3_error_5__I_O_error
      Applies to NetApp XCP Migration Tool Issue nfs3 error 5: I/O error is reported when reading file from source during xcp copy. 2022-07-09 17:22:22,406 - ERROR - 26179 [child] ppid (000) xcp copying 'TE...Applies to NetApp XCP Migration Tool Issue nfs3 error 5: I/O error is reported when reading file from source during xcp copy. 2022-07-09 17:22:22,406 - ERROR - 26179 [child] ppid (000) xcp copying 'TEXT' nfs3 READ '10.xx.xx.xx:/mnt/text' offset 0 count 65536: nfs3 error 5: I/O error : 10.xx.xx.xx:/mnt/text XCP sync fails with one error " Unreadable files : 1"
    • NTLM fails despite RequireSeal:1 on DCs for CVE-2022-38023
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NTLM_fails_despite_RequireSeal1_on_DCs_for_CVE-2022-38023
      This article describes multiple causes for CIFS share access failure via NTLM authentication, NETLOGIN service.
    • NFS Clients are unable to see specific files in a Flexgroup volume on ONTAP
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_Clients_are_unable_to_see_specific_files_in_a_Flexgroup_volume_on_ONTAP
      NFS Clients which use OS flavor other than Solaris are unable to see files in the directories . Empty directory that could not be deleted as it contained an invisible file (the client does not display...NFS Clients which use OS flavor other than Solaris are unable to see files in the directories . Empty directory that could not be deleted as it contained an invisible file (the client does not display it, even with "ls -la") 1) CentOS Linux release 7.6.1810 (Core) doesn't show the file link_file.sv 2) Red Hat Enterprise Linux Workstation release 6.7 (Santiago) doesn't show the file link_file.sv 3) From Solaris it shows fileid as 0 for file link_file.sv and it is visible
    • secd.lsa.noServers because SMB2 for dc connections is disabled
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/secd_lsa_noServers_because_SMB2__for_dc_connections_is_disabled
      6/25/2021 10:40:45 node-02 EMERGENCY secd.lsa.noServers: None of the LSA servers configured for Vserver (svm_02) are currently accessible via the network. 6/25/2021 10:36:41 node-01 EMERGENCY secd.lsa...6/25/2021 10:40:45 node-02 EMERGENCY secd.lsa.noServers: None of the LSA servers configured for Vserver (svm_02) are currently accessible via the network. 6/25/2021 10:36:41 node-01 EMERGENCY secd.lsa.noServers: None of the LSA servers configured for Vserver (svm_01) are currently accessible via the network. Note: In ONTAP 9.1, SMB version 2.0 can be enabled to connect to a domain controller, which is requried if SMB 1.0 is disabled on domain controllers.