Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 15 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
    • Filename is created with non-utf-8 code on the utf-8 volume, some multi-byte character is showing garbled
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/filename_is_created_with_non-UTF-8_code_on_the_UTF-8_languages_volume
      Applies to ONTAP 9 Issue Create filename from NFS client with non-UTF-8 characters into UTF-8 volume, some characters are showing garbled. Example: Volume language code set as C.UTF-8 Linux clients ac...Applies to ONTAP 9 Issue Create filename from NFS client with non-UTF-8 characters into UTF-8 volume, some characters are showing garbled. Example: Volume language code set as C.UTF-8 Linux clients access via NFSv3 and create a filename using a non-UTF-8 language, such as euc-jp. Check filename by ls command, the file name shows garbled. A file with a file name containing a specific character string cannot be written to the NFS mounted area.
    • NFS access is getting denied after enabling "auth-sys-extended-groups"
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_access_is_getting_denied_after_enabling_auth-sys-extended-groups
      After enabling the NFS option auth-sys-extended-groups, the NFS access from client is getting denied secd.authsys.lookup.failed:error: Unable to retrieve credentials for UNIX user with UID (x) on Vser...After enabling the NFS option auth-sys-extended-groups, the NFS access from client is getting denied secd.authsys.lookup.failed:error: Unable to retrieve credentials for UNIX user with UID (x) on Vserver (SVM) for client with IP address (y). 816053 NFS 124 16 V3 ACCESS Call (Reply In 816054), FH: 0x552b00cd, [Check: RD LU MD XT DL] 816054 NFS 24 16 V3 ACCESS Reply (Call In 816053) RPC Auth Error: (client must begin new session)
    • Unable to modify the ACL permission after enabled Seal/Signing for MS-LDAP
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_modify_the_ACL_permission_after_enabled_Seal_Signing_for_MS-LDAP
      Unable to modify ACL permission after enabling LDAP signing/seal [kern_secd:info:17440] [ 2771] Unable to SASL bind to LDAP server using GSSAPI: Can't contact LDAP server [000.298.711] ERR : Unable to...Unable to modify ACL permission after enabling LDAP signing/seal [kern_secd:info:17440] [ 2771] Unable to SASL bind to LDAP server using GSSAPI: Can't contact LDAP server [000.298.711] ERR : Unable to SASL bind to LDAP server using GSSAPI: Local error { in ldapSaslBindGssapi() at src/connection_manager/secd_connection.cpp:575 } Client presents "The program cannot open the required dialog box because it cannot determine whether the computer named "host" is joined to a domain"
    • MDV staging volume is full due to continual panic of Consolidation process
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/MDV_staging_volume_is_full_due_to_continual_panic_of_Consolidation_process
      Applies to MDV staging volume is full and EMS log records error: [node01: AuditWorkerThread01: adt.stgvol.nospace:EMERGENCY]: Audit subsystem internal error: Staging volume MDV_aud_0add1c65984e43ad70c...Applies to MDV staging volume is full and EMS log records error: [node01: AuditWorkerThread01: adt.stgvol.nospace:EMERGENCY]: Audit subsystem internal error: Staging volume MDV_aud_0add1c65984e43ad70ca122eff76b1ac is full. EMS log records amount of Consolidation process panic: Thu Jul 01 00:23:53 JST [xxxx: adtconsolidation: ucore.panicString:error]: 'adtconsolidation: Received SIGSEGV (Signal 11) at RIP 0x703c2135c accessing address 0x7e4534dd0 (pid 23838, uid 0, timestamp 1625066633)'
    • If preferred DC goes offline, does ONTAP tries to connect to other discovered DC for authentication?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/If_preferred_DC_goes_offline_does_ONTAP_tries_to_connect_to_other_discovered_DC_for_authentication
      Applies to ONTAP 9 Answer Yes, ONTAP tries to connect to other discovered DC for authentication if discovery mode is set to all or site even if preferred DC goes offline. Additional Information What i...Applies to ONTAP 9 Answer Yes, ONTAP tries to connect to other discovered DC for authentication if discovery mode is set to all or site even if preferred DC goes offline. Additional Information What is Domain Controller Discovery?
    • How to verify whether the Signing/Seal and LDAPS are enabled from Secd log
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_verify_whether_the_Signing_Seal_and_LDAPS_are_enabled_from_Secd_log
      Applies to ONTAP 9 Description How to verify whether the Signing/Seal & LDAPS are enabled from Secd log.
    • ONTAP does not alert "quota.exceeded" for hard limit in CIFS operations
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/ONTAP_does_not_alert_quota_exceeded_for_hard_limit_in_CIFS_operations
      Applies to ONTAP 9 Quotas Issue ONTAP does not detect quota.exceeded though the quota hard limit is exceeded when: CIFS share is created with qtree path. The files size is larger than quota hard limit...Applies to ONTAP 9 Quotas Issue ONTAP does not detect quota.exceeded though the quota hard limit is exceeded when: CIFS share is created with qtree path. The files size is larger than quota hard limit.
    • What is the Volume and qtree name restriction
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_is_the_Volume_and_qtree_name_restriction
      In addition, using some special characters in qtree names, such as commas and spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. Beginning with ONTAP 9.5, support fo...In addition, using some special characters in qtree names, such as commas and spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. Beginning with ONTAP 9.5, support for 4-byte UTF-8 encoded names enables the creation and display of the file, directory, and tree names that include Unicode supplementary characters outside the Basic Multilingual Plane (BMP). How ONTAP handles multi-byte file, directory, and qtree names
    • What does "showmount.update.failed" message mean?
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_does_showmount_update_failed_message_mean
      The corrective action is to verify that the root volume of the Vserver is online and not full. Execute "volume show -vserver <vserver_name> -volume <root_volume_name> -fields state" command to check t...The corrective action is to verify that the root volume of the Vserver is online and not full. Execute "volume show -vserver <vserver_name> -volume <root_volume_name> -fields state" command to check the root volume is online Execute "df -V -vserver <vserver_name> -volume <root_volume_name>" to confirm that the volume usage rate is not Full In the above example, the root volume is vol0, and percent-used-space is 0% this means it's not full.
    • Change the instance type(from c4.xx to other) from Cloud Manager is failed
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Changing__of_the_C4.xx_instance_to_other_type__of_instance_from
      Applies to NetApp Cloud Volumes ONTAP (CVO) for AWS NetApp Cloud Manager Issue Change the instance type(from c4.xx to other) from Cloud Manager is failed