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

[Tahereh Fattahi]

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 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 create,
>> for video files. Am I correct?
>>
>
> How consistent should it be? May be you can do this operation on another
> thread or something in the background so that your application may not see
> the delay in doing I/O?
>
>
>>
>> On Mon, Jun 5, 2017 at 11:28 AM, Pranith Kumar Karampuri <
>> pkara...@redhat.com> wrote:
>>
>>> 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 that the application can use it. I don't think this
>>> doesn't look like the job of index xlator either.
>>>
>>> Why do you not want to set the extended attribute from client and want
>>> the fs to do it on-behalf of the application? Setting it from client has
>>> benefits like even when one brick is down it will automatically heal this
>>> extended attribute etc.
>>>
>>> On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi 
>>> wrote:
>>>
 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 <
> t28.fatt...@gmail.com> 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 information? Or do you want this on
> mount?
>
>
>>
>> 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 Fattahi <
>>> t28.fatt...@gmail.com> 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 want this attribute be set by
 server not by client.
 I dont know which xlator is suitable for this work.

>>>
>>> The xlator that comes close to it is:  index xlator
>>> xlators/features/index/src
>>>
>>> You may have to track extra operations like
>>> create/mknod/link/rename/unlink to make sure you get the
>>> functionality you want. Basically this xlator helps you in indexing a
>>> behavior. We use this for indexing directories/files that need heal etc.
>>>
>>>

 On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
 pkara...@redhat.com> wrote:

> 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 trying to solve.
>
> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi <
> t28.fatt...@gmail.com> wrote:
>
>> 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 function (when there is a create 
>> request for a
>> video file).
>> question is about client knowledge about this variable. is it
>> possible that client can see the amount of this variable of different
>> servers (bricks) and OR them to one variable in cient's inode of the
>> directory? in which xlator I should try in client side?
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Pranith
>


>>>
>>>
>>> --
>>> Pranith
>>>
>>
>>
>
>
> --
> 

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

[Pranith Kumar Karampuri]

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 create,
> for video files. Am I correct?
>

How consistent should it be? May be you can do this operation on another
thread or something in the background so that your application may not see
the delay in doing I/O?


>
> On Mon, Jun 5, 2017 at 11:28 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> 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 that the application can use it. I don't think this
>> doesn't look like the job of index xlator either.
>>
>> Why do you not want to set the extended attribute from client and want
>> the fs to do it on-behalf of the application? Setting it from client has
>> benefits like even when one brick is down it will automatically heal this
>> extended attribute etc.
>>
>> On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi 
>> wrote:
>>
>>> 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 I access to variable in index xlator in client side?
> is it correct? getfattr trusted.index.myvar
>

 To which xlator do you want this information? Or do you want this on
 mount?


>
> 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 Fattahi <
>> t28.fatt...@gmail.com> 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 want this attribute be set by
>>> server not by client.
>>> I dont know which xlator is suitable for this work.
>>>
>>
>> The xlator that comes close to it is:  index xlator
>> xlators/features/index/src
>>
>> You may have to track extra operations like
>> create/mknod/link/rename/unlink to make sure you get the
>> functionality you want. Basically this xlator helps you in indexing a
>> behavior. We use this for indexing directories/files that need heal etc.
>>
>>
>>>
>>> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
>>> pkara...@redhat.com> wrote:
>>>
 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 trying to solve.

 On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi <
 t28.fatt...@gmail.com> wrote:

> 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 function (when there is a create request for a 
> video
> file).
> question is about client knowledge about this variable. is it
> possible that client can see the amount of this variable of different
> servers (bricks) and OR them to one variable in cient's inode of the
> directory? in which xlator I should try in client side?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Pranith Kumar Karampuri]

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 that the application can use it. I don't think this
doesn't look like the job of index xlator either.

Why do you not want to set the extended attribute from client and want the
fs to do it on-behalf of the application? Setting it from client has
benefits like even when one brick is down it will automatically heal this
extended attribute etc.

On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi 
wrote:

> 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 I access to variable in index xlator in client side?
>>> is it correct? getfattr trusted.index.myvar
>>>
>>
>> To which xlator do you want this information? Or do you want this on
>> mount?
>>
>>
>>>
>>> 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 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 want this attribute be set by server
> not by client.
> I dont know which xlator is suitable for this work.
>

 The xlator that comes close to it is:  index xlator
 xlators/features/index/src

 You may have to track extra operations like
 create/mknod/link/rename/unlink to make sure you get the functionality
 you want. Basically this xlator helps you in indexing a behavior. We use
 this for indexing directories/files that need heal etc.


>
> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> 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 trying to solve.
>>
>> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi <
>> t28.fatt...@gmail.com> wrote:
>>
>>> 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 function (when there is a create request for a 
>>> video
>>> file).
>>> question is about client knowledge about this variable. is it
>>> possible that client can see the amount of this variable of different
>>> servers (bricks) and OR them to one variable in cient's inode of the
>>> directory? in which xlator I should try in client side?
>>>
>>> ___
>>> Gluster-devel mailing list
>>> Gluster-devel@gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>>
>>
>>
>>
>> --
>> Pranith
>>
>
>


 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Tahereh Fattahi]

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 I access to variable in index xlator in client side?
>> is it correct? getfattr trusted.index.myvar
>>
>
> To which xlator do you want this information? Or do you want this on mount?
>
>
>>
>> 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 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 want this attribute be set by server
 not by client.
 I dont know which xlator is suitable for this work.

>>>
>>> The xlator that comes close to it is:  index xlator
>>> xlators/features/index/src
>>>
>>> You may have to track extra operations like
>>> create/mknod/link/rename/unlink to make sure you get the functionality
>>> you want. Basically this xlator helps you in indexing a behavior. We use
>>> this for indexing directories/files that need heal etc.
>>>
>>>

 On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
 pkara...@redhat.com> wrote:

> 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 trying to solve.
>
> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi  > wrote:
>
>> 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 function (when there is a create request for a 
>> video
>> file).
>> question is about client knowledge about this variable. is it
>> possible that client can see the amount of this variable of different
>> servers (bricks) and OR them to one variable in cient's inode of the
>> directory? in which xlator I should try in client side?
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Pranith
>


>>>
>>>
>>> --
>>> Pranith
>>>
>>
>>
>
>
> --
> Pranith
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Pranith Kumar Karampuri]

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 information? Or do you want this on mount?


>
> 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 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 want this attribute be set by server
>>> not by client.
>>> I dont know which xlator is suitable for this work.
>>>
>>
>> The xlator that comes close to it is:  index xlator
>> xlators/features/index/src
>>
>> You may have to track extra operations like create/mknod/link/rename/unlink
>> to make sure you get the functionality you want. Basically this xlator
>> helps you in indexing a behavior. We use this for indexing
>> directories/files that need heal etc.
>>
>>
>>>
>>> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
>>> pkara...@redhat.com> wrote:
>>>
 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 trying to solve.

 On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi 
 wrote:

> 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 function (when there is a create request for a video
> file).
> question is about client knowledge about this variable. is it possible
> that client can see the amount of this variable of different servers
> (bricks) and OR them to one variable in cient's inode of the directory? in
> which xlator I should try in client side?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Tahereh Fattahi]

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 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 want this attribute be set by server not
>> by client.
>> I dont know which xlator is suitable for this work.
>>
>
> The xlator that comes close to it is:  index xlator
> xlators/features/index/src
>
> You may have to track extra operations like create/mknod/link/rename/unlink
> to make sure you get the functionality you want. Basically this xlator
> helps you in indexing a behavior. We use this for indexing
> directories/files that need heal etc.
>
>
>>
>> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
>> pkara...@redhat.com> wrote:
>>
>>> 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 trying to solve.
>>>
>>> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi 
>>> wrote:
>>>
 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 function (when there is a create request for a video
 file).
 question is about client knowledge about this variable. is it possible
 that client can see the amount of this variable of different servers
 (bricks) and OR them to one variable in cient's inode of the directory? in
 which xlator I should try in client side?

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://lists.gluster.org/mailman/listinfo/gluster-devel

>>>
>>>
>>>
>>> --
>>> Pranith
>>>
>>
>>
>
>
> --
> Pranith
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Pranith Kumar Karampuri]

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 want this attribute be set by server not
> by client.
> I dont know which xlator is suitable for this work.
>

The xlator that comes close to it is:  index xlator
xlators/features/index/src

You may have to track extra operations like create/mknod/link/rename/unlink
to make sure you get the functionality you want. Basically this xlator
helps you in indexing a behavior. We use this for indexing
directories/files that need heal etc.


>
> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> 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 trying to solve.
>>
>> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi 
>> wrote:
>>
>>> 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 function (when there is a create request for a video file).
>>> question is about client knowledge about this variable. is it possible
>>> that client can see the amount of this variable of different servers
>>> (bricks) and OR them to one variable in cient's inode of the directory? in
>>> which xlator I should try in client side?
>>>
>>> ___
>>> Gluster-devel mailing list
>>> Gluster-devel@gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>>
>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Tahereh Fattahi]

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 for this work.

On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri  wrote:

> 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
> trying to solve.
>
> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi 
> wrote:
>
>> 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 function (when there is a create request for a video file).
>> question is about client knowledge about this variable. is it possible
>> that client can see the amount of this variable of different servers
>> (bricks) and OR them to one variable in cient's inode of the directory? in
>> which xlator I should try in client side?
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Pranith
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

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

[Pranith Kumar Karampuri]

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
trying to solve.

On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi 
wrote:

> 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 function (when there is a create request for a video file).
> question is about client knowledge about this variable. is it possible
> that client can see the amount of this variable of different servers
> (bricks) and OR them to one variable in cient's inode of the directory? in
> which xlator I should try in client side?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Adding one variable to inode structure

[Tahereh Fattahi]

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 function (when there is a create request for a video file).
question is about client knowledge about this variable. is it possible that
client can see the amount of this variable of different servers (bricks)
and OR them to one variable in cient's inode of the directory? in which
xlator I should try in client side?
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel