<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Jan,<br>
<br>
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.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks,<br>
Anh Dao<o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">gpfsug-discuss <gpfsug-discuss-bounces@gpfsug.org> on behalf of Jan Winter <jan@mcwinter.org><br>
<b>Date: </b>Monday, August 12, 2024 at 4:43</span><span style="font-family:"Arial",sans-serif;color:black"> </span><span style="color:black">PM<br>
<b>To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>
<b>Subject: </b>[EXTERNAL] [gpfsug-discuss] ACL issue with Linux kernel NFSv3<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hello,<br>
<br>
I'm running a 5.1.9 gpfs cluster on Rocky Linux 8, what we recently <br>
updated from Centos 7.<br>
Since then I notice that ACL inhered permission are not getting applied <br>
to new created directory's via NFS.<br>
<br>
As an example, we exporting a space<br>
/path/to/space<br>
<br>
This space has posix permission + some extra ACL:<br>
<br>
group:some-extra-groups:rwxc:allow:FileInherit:DirInherit<br>
(X)READ/LIST (X)WRITE/CREATE (X)APPEND/MKDIR (X)SYNCHRONIZE <br>
(X)READ_ACL (X)READ_ATTR (X)READ_NAMED<br>
(X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH <br>
(X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED<br>
<br>
If I create a new file on the NFS client, the ACL get applied, but when <br>
I create a new directory the ACL are missing.<br>
<br>
I didn't had this problem with Centos 7, does anyone here have an idea <br>
what the problem could be, or a way how to debug this issue?<br>
<br>
Regards<br>
Jan<br>
<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at gpfsug.org<br>
</span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org"><span style="font-size:11.0pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</span></a><span style="font-size:11.0pt">
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>