Re: [Gluster-devel] Adding one variable to inode structure

Thank you very much But if it was like trusted.glusterfs.dht or trusted.glusterfs.qouta it was more better. On Mon, Jun 5, 2017 at 2:58 PM, Pranith Kumar Karampuri wrote: > > > On Mon, Jun 5, 2017 at 12:40 PM, Tahereh Fattahi > wrote: > >> yes you

Re: [Gluster-devel] Adding one variable to inode structure

On Mon, Jun 5, 2017 at 12:40 PM, Tahereh Fattahi wrote: > yes you are correct. > I thought that for creating a video file i first should do a getfattr, if > it was not set then I should do a setxattr. > So it would be have bad performance to do a getfattr after every

Re: [Gluster-devel] Adding one variable to inode structure

Oh you want applications to do getfattr to find that it is there? I think I understood what you are looking for now. So basically applications will keep doing creation of some files/directories, whenever a video file is created you want the bricks to set an extended attribute on the directory, so

Re: [Gluster-devel] Adding one variable to inode structure

I want in in mount directory in client side On Mon, Jun 5, 2017 at 11:07 AM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > > > On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi > wrote: > >> Thank you >> I see that this xlator is loaded in server side. >> How can

Re: [Gluster-devel] Adding one variable to inode structure

On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi wrote: > Thank you > I see that this xlator is loaded in server side. > How can I access to variable in index xlator in client side? > is it correct? getfattr trusted.index.myvar > To which xlator do you want this

Re: [Gluster-devel] Adding one variable to inode structure

Thank you I see that this xlator is loaded in server side. How can I access to variable in index xlator in client side? is it correct? getfattr trusted.index.myvar On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > > > On Mon, Jun 5, 2017 at 9:55 AM, Tahereh

Re: [Gluster-devel] Adding one variable to inode structure

On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi wrote: > Assume that one client wants to search it's directories for video files. > I want use something that helps this client to search just directories > that have this kind of file. > like a extended attribute, but I

Re: [Gluster-devel] Adding one variable to inode structure

Assume that one client wants to search it's directories for video files. I want use something that helps this client to search just directories that have this kind of file. like a extended attribute, but I want this attribute be set by server not by client. I dont know which xlator is suitable

Re: [Gluster-devel] Adding one variable to inode structure

This sounds hacky. In general anything that is specific about an inode, we try to store it in inode-ctx. Who uses this information about presence of video-file and how? May be with that knowledge there could be a possibility we can improve the solution. Do let us know the complete problem you are

[Gluster-devel] Adding one variable to inode structure

Hi I want to add one boolean field to inode structure for a directory. when it is 1 it means that directory has one or more video file. when it is 0 it means that there is no video file in that directory. I can add this variable to inode structure and update it in server side, in posix_create