On 12/11/2011 12:25 AM, Brian Rosner wrote:
Here is my setup:
Volume Name: g-data-instances
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.x.x.106:/var/g/data-instances
Brick2: 10.x.x.131:/var/g/data-instances
Brick3: 10.x.x.0:/var/g/data-instances
Brick4: 10.x.x.201:/var/g/data-instances
running on 3.2.5. The client is mounted:
mount -t glusterfs 10.x.x.106:/g-data-instances /mnt
I am seeing:
[2011-12-10 18:45:24.792339] I
[client3_1-fops.c:818:client3_1_setxattr_cbk]
0-g-data-instances-client-0: remote operation failed: Permission
denied
[2011-12-10 18:45:24.792502] I
[client3_1-fops.c:818:client3_1_setxattr_cbk]
0-g-data-instances-client-1: remote operation failed: Permission
denied
[2011-12-10 18:45:24.795528] W [fuse-bridge.c:1348:fuse_rename_cbk]
0-glusterfs-fuse: 484: /i130/xapian/position.tmp ->
/i130/xapian/position.baseB => -1 (Permission denied)
I have tried to produce this in other ways such as:
sudo -u i130 bash -c "umask 027 ; python"
open("/mnt/i130/xapian/a", "wb").write("hello")
import os
os.rename("/mnt/i130/xapian/a", "/mnt/i130/xapian/b")
however, this example works flawlessly. I've tracked down the line of
code in xapian which is seeing the error and it looks to be a
straightforward rename system call.
Does anyone have ideas on what I can try to resolve this issue?
Seems like the issue with that specific file your application is trying
to rename. Could you check if that file has correct permissions on the
backends?.
Pranith
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
