I am a gluster newbie, and we don't use nfs with it, but it seems (at least to me) that if you have 2 users sharing files in a write context, especially where resulting temp file namespace may clash, having their umask group write permissions enabled would be a reasonable requirement. -----Original Message----- From: Whit Blauvelt [mailto:whit.gluster at transpect.com] Sent: Tuesday, April 19, 2011 12:05 PM To: Gally, Jerry Cc: gluster-users at gluster.org Subject: Re: gluster mounted volumes not following group permissions Jerry, Here's the thing. On the same system, with the same two users, I've just repeated the same operations on local storage, rather than nfs-mounted gluster storage, and there's no such problem. The file saves just fine after user2 edits it, resulting in: -rw-rw-r-- 1 user1 staff 8 2011-04-19 15:01 dog -rw-r--r-- 1 user2 staff 4 2011-04-19 15:01 dog~ And the file "dog" indeed contains the edit by user2, as it should. Are you suggesting that gluster uses umask settings differently than the native filesystem? In this case, the system where it works as expected is ext3 rather than the ext4 systems under gluster, but that shouldn't change this behavior I don't think. Whit On Tue, Apr 19, 2011 at 11:35:41AM -0700, Gally, Jerry wrote: > I presume that would be caused by a user1's umask setting that does not > set group write permissions on newly created files. > > -----Original Message----- > > I've just verified your report by doing the same test with 3.1.4 in an > Ubuntu 10.10 server environment, with the client mount via NFS from Ubuntu > 8.04.4. I get exactly the same result. In this case a file is first written > by user1, member of "staff" group. Then user2 opens it, adds an edit, and > tries to save. The backup (using the joe editor) shows up with user2's > ownership: > > -rw-rw-r-- 1 user1 staff 4 2011-04-19 14:23 dog > -rw-r--r-- 1 user2 staff 4 2011-04-19 14:24 dog~ > > But the save fails with "Error opening file" from the editor.
