<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 26, 2016 at 7:06 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Tue, Apr 26, 2016 at 06:45:59PM +0530, ABHISHEK PALIWAL wrote:<br>
> On Tue, Apr 26, 2016 at 6:37 PM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
><br>
> > On Tue, Apr 26, 2016 at 12:11:06PM +0530, ABHISHEK PALIWAL wrote:<br>
> > > Hi,<br>
> > ><br>
> > > I want to enable ACL support on gluster volume using the kernel NFS ACL<br>
> > > support so I have followed below steps after creation of gluster volume:<br>
> > ><br>
> > > 1. mount -t glusterfs -o acl 10.32.0.48:/c_glusterfs /tmp/a2<br>
> > ><br>
> > > 2. update the /etc/exports file<br>
> > > /tmp/a2 10.32.*(rw,acl,sync,no_subtree_check,no_root_squash,fsid=14)<br>
> > ><br>
> > > 3. exportfs –ra<br>
> > ><br>
> > > 4. gluster volume set c_glusterfs nfs.acl off<br>
> > ><br>
> > > 5. gluster volume set c_glusterfs nfs.disable on<br>
> > ><br>
> > > we have disabled above two options because we are using Kernel NFS ACL<br>
> > > support and that is already enabled.<br>
> > ><br>
> > ><br>
> > ><br>
> > > on other board mounting it using<br>
> > ><br>
> > > mount -t nfs -o acl,vers=3 10.32.0.48:/tmp/a2 /tmp/e/<br>
> > ><br>
> > > setfacl -m u:application:rw /tmp/e/usr<br>
> > > setfacl: /tmp/e/usr: Operation not supported<br>
> ><br>
> > Have you tried to set/getfacl on the Gluster FUSE mountpoint (/tmp/a2)<br>
> > too? Depending on the filesystem that you use on the bricks, you may<br>
> > need to mount with "-o acl" there as well. Try to set/get an ACL on all<br>
> > of these different levels to see where is starts to fail.<br>
> ><br>
> Yes, you can check I have already given -o acl on /tmp/a2 as well as below<br>
<br>
</span>Sorry, that is not what I meant. The bricks that provide the c_glusterfs<br>
volume need to support and have ACLs enabled as well. If you use XFS, it<br>
should be enabled by default. But some other filesystems do not do that.<br>
<br>
You have three different mountpoints:<br>
<br>
- /tmp/e: nfs<br>
- /tmp/a2: Gluster FUSE<br>
- whatever you use as bricks for c_glusterfs: XFS or something else?<br></blockquote><div><br></div><div>I have following volume info</div><div><br></div><div>Volume Name: c_glusterfs</div><div>Type: Replicate</div><div>Volume ID: 5be1524c-21ae-47d5-970a-d4920fca39cf</div><div>Status: Started</div><div>Number of Bricks: 1 x 2 = 2</div><div>Transport-type: tcp</div><div>Bricks:</div><div>Brick1: 10.32.0.48:/opt/lvmdir/c2/brick</div><div>Brick2: 10.32.1.144:/opt/lvmdir/c2/brick</div><div>Options Reconfigured:</div><div>nfs.acl: off</div><div>nfs.disable: on</div><div>network.ping-timeout: 4</div><div>performance.readdir-ahead: on</div><div><br></div><div>now according to you /opt/lvmdir/c2/brick should support ACL option or /opt/lvmdir/c2 ? if /opt/lvmdir/</div><div>c2 then we are mounting it as below</div><div><br></div><div>
<div class="">
<p class="MsoNormal" style="margin-bottom:0.0001pt"><span style="font-size:10pt;font-family:'Segoe UI',sans-serif;color:black"> mount -o acl /dev/cpplvm_vg/vol2 /opt/lvmdir//c2</span></p><p class="MsoNormal" style="margin-bottom:0.0001pt"><span style="font-size:10pt;font-family:'Segoe UI',sans-serif;color:black"><br></span></p><p class="MsoNormal" style="margin-bottom:0.0001pt"><span style="font-size:10pt;font-family:'Segoe UI',sans-serif;color:black">I have one more question : we are using logical volume here for glusterfs so it should not create any issue in ACL support?</span></p><p class="MsoNormal" style="margin-bottom:0.0001pt"><span style="font-size:10pt;font-family:'Segoe UI',sans-serif;color:black"><br></span></p><p class="MsoNormal" style="margin-bottom:0.0001pt"><span style="font-size:10pt;font-family:'Segoe UI',sans-serif;color:black">Regards,</span></p><p class="MsoNormal" style="margin-bottom:0.0001pt"><span style="font-size:10pt;font-family:'Segoe UI',sans-serif;color:black">Abhishek</span></p>
</div></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
HTH,<br>
Niels<br>
<div class=""><div class="h5"><br>
><br>
> > 1. mount -t glusterfs -o acl 10.32.0.48:/c_glusterfs /tmp/a2<br>
> ><br>
> > 2. update the /etc/exports file<br>
> > /tmp/a2 10.32.*(rw,acl,sync,no_subtree_check,no_root_squash,fsid=14)<br>
> ><br>
><br>
> ><br>
> > Thanks,<br>
> > Niels<br>
> ><br>
> > ><br>
> > > and application is the system user like below<br>
> > ><br>
> > > application:x:102:0::/home/application:/bin/sh<br>
> > ><br>
> > > I don't why I am getting this failure when I enabled all the acl support<br>
> > in<br>
> > > each steps.<br>
> > ><br>
> > > Please let me know how can I enable this.<br>
> > ><br>
> > > Regards,<br>
> > > Abhishek<br>
> ><br>
> > > _______________________________________________<br>
> > > Gluster-devel mailing list<br>
> > > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> ><br>
> ><br>
><br>
><br>
> --<br>
><br>
><br>
><br>
><br>
> Regards<br>
> Abhishek Paliwal<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><br><br><br><br>Regards<br>
Abhishek Paliwal<br>
</div></div>
</div></div>