You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if this is a server-side or client-side problem.
I have an NFS share that I mount from a Fedora 31 workstation. When I mount the share using NFSv4.2, I find that the process umask is ignored when creating files and directories within the share. Files are created with 666 permissions, and directories are created with 777 permissions. Mounting the same share with NFSv4.1 rather than 4.2 works fine.
Mount an NFSv4.2 share from OpenWrt to /mnt on Fedora
mkdir /mnt/foo
ls -ld /mnt/foo
Resulting permissions are 777, but they should be 755, due to a process umask of 0022.
MikePetullo:
I am not sure if this is a server-side or client-side problem.
I have an NFS share that I mount from a Fedora 31 workstation. When I mount the share using NFSv4.2, I find that the process umask is ignored when creating files and directories within the share. Files are created with 666 permissions, and directories are created with 777 permissions. Mounting the same share with NFSv4.1 rather than 4.2 works fine.
Resulting permissions are 777, but they should be 755, due to a process umask of 0022.
This seems related to a similar Ubuntu report:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736
I suspect this results from changes due to the RFC "Allowing Inheritable NFSv4 ACLs to Override the Umask:"
https://tools.ietf.org/id/draft-ietf-nfsv4-umask-03.html
See also https://bugzilla.redhat.com/show_bug.cgi?id=1667761 for a report on the client side.
OpenWrt SNAPSHOT, r11219-34c4741da0 on x86_64
kmod-fs-nfs - 4.19.78-1
kmod-fs-nfs-common - 4.19.78-1
kmod-fs-nfs-common-rpcsec - 4.19.78-1
kmod-fs-nfs-v4 - 4.19.78-1
kmod-fs-nfsd - 4.19.78-1
nfs-kernel-server - 2.4.1-1
nfs-utils-libs - 2.4.1-1
The text was updated successfully, but these errors were encountered: