This sounds like it could, maybe, possibly, be related to what I
encountered some time back. Bottom line is that the permission
bits of a newly created file are a logical and of the default acl
of the containing directory and the bits passed to creat. Do you
have a default acl set on the directory involved, and does it have
the bits masked off that you see as missing?
-Chip
-----Original Message-----
From: Shiv Sikand [mailto:sikand@xxxxxxxxxxxxxx]
Sent: Sunday, January 27, 2002 4:14
To: linux-xfs@xxxxxxxxxxx
Cc: chmouel@xxxxxxxxxxxxxxxx
Subject: Mandrake 8.1 exhibits xfs/nfs umask problem
We have observed that the Mandrake 8.1 kernel exhibits a umask problem when xfs
volumes are exported with nfs.
If a new directory is created via nfs on an xfs volume, the umask from the
current process is not inherited.
Reading the mail archive, it looks like this problem or something extremely
similar was fixed in the XFS tree a long time ago.
We do not observe this problem with 2.4.5-xfs-1.0.1 which has been our
production kernel prior to the arrival of XFS support in Mandrake.
Can someone please take a look at the xfs code in the Mandrake build and
confirm the problem.
Thanks,
Shiv
|