[Gluster-users] Renaming permission denied

Brian Rosner brosner at gmail.com
Wed Dec 14 22:05:59 UTC 2011

On Dec 13, 2011, at 7:54 PM, Pranith Kumar K wrote:

> On 12/13/2011 10:56 PM, Brian Rosner wrote:
>> On Dec 12, 2011, at 1:41 AM, Pranith Kumar K wrote:
>>> 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?.
>> It is difficult for me to test that due to the file being created and unlinked during the reindexing process. The fact it has permission to unlink and not rename seems very odd to me.
>> Brian Rosner
> Brian,
>   Could you give the permissions/ownership of the directory the file is being created, permissions/ownership of the file that is being created. Is the group of the file secondary group?
> It is very difficult for us to find the root cause without a good test case.

Ok, I have a bit more info. I was able to reproduce it with a tool that I can easily modify.

Here is some info from this new case:


[2011-12-14 21:53:15.373241] W [fuse-bridge.c:1348:fuse_rename_cbk] 0-glusterfs-fuse: 265: /i130/whoosh_index/_MAIN_1.toc.1323899595.36 -> /i130/whoosh_index/_MAIN_1.toc => -1 (Permission denied)

% sudo ls -l /mnt/i130/whoosh_index/_MAIN_1.toc.1323899595.36
-rw-r----- 1 1630 nogroup 1522 2011-12-14 21:52 /mnt/i130/whoosh_index/_MAIN_1.toc.1323899595.36

% sudo ls -l /mnt/i130/
drwxr-x--- 2 1630 nogroup  8192 2011-12-14 21:52 whoosh_index

% sudo ls -l /mnt | grep i130
drwxr-x--x 4      1630 anduin 8192 2011-12-14 21:52 i130

I've confirmed the user and group of the process are 1630 and nogroup.

Brian Rosner

More information about the Gluster-users mailing list