Hi,
tla 525, fuse-2.7.0-glfs4, Scientific Linux CERN SLC release 4.5 (Beryllium)
(kernel-2.6.9-55.0.2.EL.cern)
one user creates a file on glfs with permission bits 0644, another user
manipulates on it:
1) "touch" or "cat >" work right - "Permission denied"
2) "rm" and as a consequence "mv" work wrong - operation is finished
successfully :(
server spec:
=========
volume brick
type storage/posix
option directory /data/export
end-volume
# Trace storage/posix translator.
volume trace
type debug/trace
subvolumes brick
option debug on
end-volume
volume server
type protocol/server
subvolumes trace
option transport-type tcp/server
# option bind-address 172.30.2. # Default is to listen on all
interfaces
option listen-port 6996 # Default is 6996
# option client-volume-filename /etc/glusterfs/glusterfs-client.vol
option auth.ip.trace.allow 172.30.2.*
end-volume
client spec:
========
volume client
type protocol/client
option transport-type tcp/client
option remote-host 172.30.2.1
option remote-subvolume brick
end-volume
### Trace storage/posix translator.
volume trace
type debug/trace
subvolumes client
option debug on
end-volume
server log:
=======
2007-10-19 18:08:58 D [inode.c:351:__active_inode] brick/inode: activating
inode(132), lru=1/1024
2007-10-19 18:08:58 D [inode.c:381:__passive_inode] brick/inode: passivating
inode(132), lru=2/1024
2007-10-19 18:08:58 D [inode.c:351:__active_inode] brick/inode: activating
inode(132), lru=1/1024
2007-10-19 18:08:58 D [inode.c:381:__passive_inode] brick/inode: passivating
inode(132), lru=2/1024
2007-10-19 18:08:58 D [inode.c:351:__active_inode] brick/inode: activating
inode(132), lru=1/1024
2007-10-19 18:08:58 D [inode.c:308:__destroy_inode] brick/inode: destroy
inode(132) [@0x85f45a0]
client log:
=======
2007-10-19 18:08:58 D [inode.c:351:__active_inode] fuse/inode: activating
inode(132), lru=0/1024
2007-10-19 18:08:58 D [fuse-bridge.c:422:fuse_lookup] glusterfs-fuse: LOOKUP
1/bashrc (/bashrc)
2007-10-19 18:08:58 D [trace.c:971:trace_lookup] trace: callid: 11
(*this=0x86cae78, loc=0x870428c {path=/bashrc, inode=0x8704850},
need_xattr=0 )
2007-10-19 18:08:58 D [trace.c:435:trace_lookup_cbk] trace: callid: 11
(*this=0x86cae78, op_ret=0, op_errno=2, inode=0x8704850, *buf=0x87048b8
{st_dev=64768, st_ino=132, st_mode=33188, st_nlink=1, st_uid=2005,
st_gid=100, st_rdev=0, st_size=1170, st_blksize=4096, st_blocks=8})
2007-10-19 18:08:58 D [fuse-bridge.c:344:fuse_entry_cbk] glusterfs-fuse:
ENTRY => 132
2007-10-19 18:08:58 D [inode.c:381:__passive_inode] fuse/inode: passivating
inode(132), lru=1/1024
2007-10-19 18:08:58 D [fuse-bridge.c:916:fuse_unlink] glusterfs-fuse: UNLINK
1/bashrc
2007-10-19 18:08:58 D [inode.c:351:__active_inode] fuse/inode: activating
inode(132), lru=0/1024
2007-10-19 18:08:58 D [trace.c:1121:trace_unlink] trace: (*this=0x86cae78,
loc=0x870428c{path=/bashrc, inode=0x8704850})
2007-10-19 18:08:58 D [trace.c:375:trace_unlink_cbk] trace:
(*this=0x86cae78, op_ret=0, op_errno=2)
2007-10-19 18:08:58 D [inode.c:381:__passive_inode] fuse/inode: passivating
inode(132), lru=1/1024
2007-10-19 18:08:58 D [inode.c:351:__active_inode] fuse/inode: activating
inode(132), lru=0/1024
2007-10-19 18:08:58 D [inode.c:308:__destroy_inode] fuse/inode: destroy
inode(132) [@0x8704850]
where is problem?
regards, Alexey.
