From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0)
Description of problem:
I believe this has to do with nfsd running daemonize() and therefore
taking on current->fs, which init set during boot to contain the umask
022. (I believe this is a patch in RH's SysVinit rpm) Anyhow, regardless
of a user's umask, any *directory* created within an nfs mount from a
client will be created with a umask of 022!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
[ccf@compile1-dev vus]$ umask
[ccf@compile1-dev vus]$ mkdir /tmp/umask.test
[ccf@compile1-dev vus]$ ls -ld /tmp/umask.test
drwxrwxr-x 2 ccf ccf 4096 Sep 6 17:25 /tmp/umask.test
[ccf@compile1-dev vus]$ df -k /data1
Filesystem 1k-blocks Used Available Use% Mounted on
35002928 5362088 27862776 17% /data1
[ccf@compile1-dev vus]$ mount | grep data1
filer1-dev:/usr/local/export on /data1 type nfs (rw,bg,soft,addr=x.x.x.x)
[ccf@compile1-dev vus]$ mkdir /data1/vus/umask.test
[ccf@compile1-dev vus]$ ls -ld /data1/vus/umask.test
drwxr-xr-x 2 ccf ccf 4096 Sep 6
Actual Results: The directory created within the NFS mount does not honor
any umask set by any user, it will simply always create directories 022.
Expected Results: The directory permissions should have corresponded to
I also have this problem, although this is on a stock redhat , upgraded with a
stock linux kernel, patched with xfs (2.4.9), xfs was needed due the machine is
attached to a 500 Gb storage. (this size really sucks when using ext2).
I have seen postings on the kernel mailing lists
which includes a discussion whether its a kernel bug that it does not handle
umask correct (nfs wise) or if its an bug in the SysVinit package in the redhat
Closing old bugs for dead packages that have no maintainers. Please refile
against current packages/products if still relevant.