Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 8 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/New_unix_files_directories_are_created_without_read_write_or_execute_bits_set
      Applies to ONTAP 9 NFSv4 ACLs present Issue A newly created directory's / file's Read (r), Write (w), or Execute (x) bits are all unset, even for the owner ls -l for such a file begins with ----------...Applies to ONTAP 9 NFSv4 ACLs present Issue A newly created directory's / file's Read (r), Write (w), or Execute (x) bits are all unset, even for the owner ls -l for such a file begins with ----------+ ls -l for such a directory begins with d---------+ Note: The plus sign at the end of the first field signifies the presence of an ACL
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFSv4_ACL_-_Resolution_Guide
      Applies to ONTAP 9 Vserver configured with NFSv4 ACL Description This article is designed to help you get the most from your NFSv4 environment with NFSv4 ACL's
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFSv4_access_denied_even_though_ACLs_should_give_access
      Applies to NFSv4 ONTAP 9 Issue User is getting access denied even though a DACL for full permissions exists for the user.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/RHEL_clients_see_Failed_setxattr_operation__Invalid_argument
      Applies to NFSv4 ACL (Access Control List) Red Hat Enterprise Linux (RHEL) The NFS server is unable to translate the user name in the ACL and returns the error NFS4ERR_BADOWNER to the client's SETATTR...Applies to NFSv4 ACL (Access Control List) Red Hat Enterprise Linux (RHEL) The NFS server is unable to translate the user name in the ACL and returns the error NFS4ERR_BADOWNER to the client's SETATTR call This causes the client to return an "Invalid Argument" error for the setxattr operation as shown in the example below: ## Editing NFSv4 ACL for directory: /mnt/nfsv4vol Failed setxattr operation: Invalid argument Note: Group name is aaa from AD LDAP and domain name is xxx.yyy
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/What_makes_up_an_NFSv4_ACL
      Applies to ONTAP 9 Vserver configured with NFSv4 ACL Description The NFSv4 ACL is formatted into several parts, split by colons. type:flags:principal:permissions Example: A:g:users@nfsacl.local:rwadtT...Applies to ONTAP 9 Vserver configured with NFSv4 ACL Description The NFSv4 ACL is formatted into several parts, split by colons. type:flags:principal:permissions Example: A:g:users@nfsacl.local:rwadtTnNcCy
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Copyed_file_inherit_parent_directory_s_Unix_permission
      mode: 0666, Name: Unknown, Read permission for owner, Write permission for owner, Read permission for group, Write permission for group, Read permission for others, Write permission for others mode: 0...mode: 0666, Name: Unknown, Read permission for owner, Write permission for owner, Read permission for group, Write permission for group, Read permission for others, Write permission for others mode: 0777, Name: Unknown, Read permission for owner, Write permission for owner, Execute permission for owner, Read permission for group, Write permission for group, Execute permission for group, Read permission for others, Write permissi
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/git_clone_in_an_NFS_export_results_in_fetch_pack__invalid_index_pack_output
      Applies to ONTAP 9 NFSv4 ACLs in use Issue When attempting git clone in an NFS export, the fetch-pack process cannot complete normally
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFSv3_permission_denied_when_inheritable_v4_ACE_is_present
      Applies to ONTAP 9 NFSv3 NFSv4 ACLs Issue When a file owner performs writes to their file from an NFSv3 client, permission is always allowed if no v4 ACL is present on that file (regardless of mode bi...Applies to ONTAP 9 NFSv3 NFSv4 ACLs Issue When a file owner performs writes to their file from an NFSv3 client, permission is always allowed if no v4 ACL is present on that file (regardless of mode bits) When a newly created file inherits an NFSv4 ACL, NFSv3 clients may be denied even if it's the owner attempting the write