<meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://bugs.gluster.com/show_bug.cgi?id=2818">http://bugs.gluster.com/show_bug.cgi?id=2818</a> - a bug is applied, easily reproducible through the steps mentioned in the bug . <div>
<br></div><div>Native FUSE works. </div><div><br><div class="gmail_quote">On Tue, Apr 19, 2011 at 3:11 PM, Whit Blauvelt <span dir="ltr"><<a href="mailto:whit.gluster@transpect.com">whit.gluster@transpect.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Jerry,<br>
<br>
You might well be right. But why would the nfs requirement be different from<br>
the shared-file-on-local-storage requirement here? The file's perms are 664.<br>
So every group member should be able to write to it - and can on local<br>
storage. But they can't on gluster-via-nfs. Both cases are users sharing<br>
files in a write context.<br>
<br>
In any case the docs at<br>
<a href="http://gluster.com/community/documentation/index.php/Gluster_3.1_NFS_Guide" target="_blank">http://gluster.com/community/documentation/index.php/Gluster_3.1_NFS_Guide</a><br>
say nothing about setting gluster's nfs service for a umask. Doesn't posix<br>
call for consistent behavior here? 664 perms should allow group members to<br>
edit the file no matter how the file system is mounted, shouldn't they? A<br>
umask in my experience is for default perms on file creation. The file here<br>
already exists with other perms. It may well be the case that we don't want<br>
files to be group-editable by default, but we certainly do when the perms<br>
are set for that.<br>
<br>
Best,<br>
<font color="#888888">Whit<br>
</font><div class="im"><br>
<br>
On Tue, Apr 19, 2011 at 02:06:50PM -0700, Gally, Jerry wrote:<br>
> I am a gluster newbie, and we don't use nfs with it, but it seems (at<br>
> least to me) that if you have 2 users sharing files in a write context,<br>
> especially where resulting temp file namespace may clash, having their<br>
> umask group write permissions enabled would be a reasonable requirement.<br>
><br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://gluster.org/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://gluster.org/cgi-bin/mailman/listinfo/gluster-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><pre cols="72"><span style="white-space:normal"><i><pre cols="72" style="text-align:left"><font face="'courier new', monospace">Harsha</font></pre>
<pre cols="72" style="text-align:left"><font face="'courier new', monospace">Gluster Inc</font></pre></i></span></pre></blockquote><br>
</div>