[gpfsug-discuss] ACL issue with Linux kernel NFSv3

ScottG scottg at emailhosting.com
Tue Aug 13 17:32:49 BST 2024


Hi Jan,
Can you please try to mount the share with the NOACL option.  that
should/will resolve the issue.

Scott Goldman

 
-----Original Message-----
From: scale <scale at us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at gpfsug.org>
To: gpfsug main discussion list <gpfsug-discuss at gpfsug.org>, Anh Dao
<adao at ibm.com>
Subject: Re: [gpfsug-discuss] ACL issue with Linux kernel NFSv3
Date: 08/13/2024 12:24:34 PM




Hi Jan,

It could be that the ACL is being overwritten for the directory after
it has been created. Another possibility is that the NFSv3 client may
not interpret the ACL correctly since NFSv4 ACL is involved. Also,
since v3 is used, the Linux kernel NFSv3 server assumes that the
filesystem has POSIX ACL. I suggest opening a ticket for this issue
with the IBM Scale support team for further investigation.

Thanks,
Anh Dao



From:gpfsug-discuss <gpfsug-discuss-bounces at gpfsug.org> on behalf of
Jan Winter <jan at mcwinter.org>
Date: Monday, August 12, 2024 at 4:43 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: [EXTERNAL] [gpfsug-discuss] ACL issue with Linux kernel NFSv3

Hello,

I'm running a 5.1.9 gpfs cluster on Rocky Linux 8, what we recently 
updated from Centos 7.
Since then I notice that ACL inhered permission are not getting applied
to new created directory's via NFS.

As an example, we exporting a space
/path/to/space

This space has posix permission + some extra ACL:

group:some-extra-groups:rwxc:allow:FileInherit:DirInherit
  (X)READ/LIST (X)WRITE/CREATE (X)APPEND/MKDIR (X)SYNCHRONIZE 
(X)READ_ACL  (X)READ_ATTR  (X)READ_NAMED
  (X)DELETE    (X)DELETE_CHILD (X)CHOWN        (X)EXEC/SEARCH 
(X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED

If I create a new file on the NFS client, the ACL get applied, but when
I create a new directory the ACL are missing.

I didn't had this problem with Centos 7, does anyone here have an idea 
what the problem could be, or a way how to debug this issue?

Regards
Jan

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20240813/b1513628/attachment.htm>


More information about the gpfsug-discuss mailing list