intended behavior filter translator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

Can someone enlighten me about the intended behavior of the filter
translator? From the documentation, I thought it would behave the same as
NFS mapping/squashing. However, this is not what I see in my setup.

Let's say I map everything to UID 1500 - using either the fixed-uid or the
translate-uid and gid option. Now, on the client side, every file and
directory appears to be owned by 1500. If I try to create new files or
directories as uid 1001 this fails because of a lack of permission.  If I
chmod 777 a directory then user 1001 can create new files/directories but
cannot change them afterwards as they appear to be owned by 1500. On the
server side, those files are owned by 1001. This is exactly opposite of NFS.
There mapping everything to 1500 has the result that every file created by
1001 is owned by uid 1500, but 1001 can change these files since his uid is
mapped to 1500.

Am I doing something wrong or is this intended behavior? I have tried
loading the filter translator on both the client and the server side. They
both give the same result. The end goal is to have every user in the network
write and read each other's files. I thought uid mapping would be the best
way to do this.

Thanks!

Ate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://zresearch.com/pipermail/gluster-users/attachments/20090618/8c3b91ad/attachment.htm>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux