(IMO) NFSv4 ACLs are complicated. Confusing. Difficult. Befuddling.
PIA. Before questioning the GPFS implementation, see how they work in
other file systems.
If GPFS does it differently, perhaps there is a rationale, or perhaps
you've found a bug.
Yes, that is the intended behavior. As in the section on traditional ACLs
that you found, the intent is that if there is a default/inherited ACL, the
object is created with that (and if there is no default/inherited ACL, then
the mode and umask are the basis for the initial set of permissions).
Hello,
The GPFS Day of the HPCXXL conference is confirmed for Thursday,
September 28th. Here is an updated URL, the agenda and registration are still
being put together
http://hpcxxl.org/summer-2017-meeting-september-24-29-new-york-city/
Hello,
I am currently trying to understand an issue with ACLs and how GPFS handles the
umask.
The filesystem is configured for NFS4 ACLs only (-k nfs4), filesets have been
configured for chmodAndUpdateACL and the access is through a native GPFS client
(v4.2.3).
If I create a new file in a
tic mount option
> -o none Additional mount options
> -T /fs_gpfs01 Default mount point
> --mount-priority 0Mount priority
>
>
>
> I saw this thread:
> https://serverfault.com/questions/655112/nfsv4-acls-on-gpfs/722200
>
> Is it still
