On 06/23/2015 04:45 AM, Vijay Bellur wrote: > On Monday 22 June 2015 01:21 PM, Atin Mukherjee wrote: >> As far as I know we would need privileged container otherwise extended >> attribute support becomes unavailable. And gluster is built on >> underlying file system which has extended attribute support. >> > > The call that seems to fail here is setattr and setxattr. So could it be > a different problem? I've tested this again and it seems like if we use unprivileged containers, set(x)attr calls fail, this is what I got for a volume creation request on that container: [root@8f267d6c6146 glusterfs]# gluster v create test-vol 172.17.0.1:/tmp/b1 force volume create: test-vol: failed: Glusterfs is not supported on brick: 172.17.0.1:/tmp/b1. Setting extended attributes failed, reason: Operation not permitted. > > >> On Jun 22, 2015 10:45 PM, "Ale" <ale975@xxxxxxxxx >> <mailto:ale975@xxxxxxxxx>> wrote: >> > >> > Hi all, >> > >> > I'm new to gluster, and recently I setup two server to use with lxc. >> > From both server I'm able to mount the volume and do normal operation. >> > >> > When I try to create a unprivileged container where the path is >> inside the gluster volume, the operation fail because unable to do >> chown operation. >> > >> > In detail lxc execute the following command: >> > >> > lxc-usernsexec -m u:0:165536:1 -m u:9869:9869:1 -m g:0:165536:1 -m >> g:9869:9869:1 -- chown 0:9869 /mnt/vm/lxc/test1 >> > >> > and the gluster log report the following error: >> > >> > [2015-06-22 16:58:44.065941] W >> [client-rpc-fops.c:2145:client3_3_setattr_cbk] 2-gv0-client-0: remote >> operation failed: Operation not permitted >> > [2015-06-22 16:58:44.066213] W >> [client-rpc-fops.c:2145:client3_3_setattr_cbk] 2-gv0-client-1: remote >> operation failed: Operation not permitted >> > [2015-06-22 16:58:44.066928] W [fuse-bridge.c:1079:fuse_setattr_cbk] >> 0-glusterfs-fuse: 36942426: SETATTR() /lxc/test1 => -1 (Operation not >> permitted) >> > >> > If I exec the same command on the local filesystem, all works fine, >> I'm running glusterfs 3.6.3 on ubuntu 14.04. >> > >> > Do you have any suggestion? > > Can you check the brick log to determine the translator that might be > reporting this error? I suspect that it could be stemming from posix. > > -Vijay > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > -- ~Atin _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
