On Tue, Jan 26, 2016 at 08:51:37AM +0100, Xavier Hernandez wrote:
> Hi Pranith,
>
> On 26/01/16 03:47, Pranith Kumar Karampuri wrote:
> >hi,
> > Traditionally gluster has been using ctime/mtime of the
> >files/dirs on the bricks as stat output. Problem we are seeing with this
> >approach is
@redhat.com>, "Gluster Devel"
<gluster-devel@gluster.org>
Sent: Tuesday, January 26, 2016 2:09:43 PM
Subject: Re: [Gluster-devel] distributed files/directories and [cm]time updates
Hi Joseph,
On 26/01/16 09:07, Joseph Fernandes wrote:
Answer inline:
- Original Message -
Fro
uster.org>
Sent: Tuesday, January 26, 2016 2:09:43 PM
Subject: Re: [Gluster-devel] distributed files/directories and [cm]time updates
Hi Joseph,
On 26/01/16 09:07, Joseph Fernandes wrote:
> Answer inline:
>
>
> - Original Message -
> From: "Xavier Hernandez" <
"Gluster Devel"
<gluster-devel@gluster.org>
Sent: Tuesday, January 26, 2016 1:21:37 PM
Subject: Re: [Gluster-devel] distributed files/directories and [cm]time updates
Hi Pranith,
On 26/01/16 03:47, Pranith Kumar Karampuri wrote:
hi,
Traditionally gluster has been using ctime/mtim
Answer inline:
- Original Message -
From: "Xavier Hernandez" <xhernan...@datalab.es>
To: "Pranith Kumar Karampuri" <pkara...@redhat.com>, "Gluster Devel"
<gluster-devel@gluster.org>
Sent: Tuesday, January 26, 2016 1:21:37 PM
Subject: R
g>
Sent: Tuesday, January 26, 2016 1:21:37 PM
Subject: Re: [Gluster-devel] distributed files/directories and [cm]time updates
Hi Pranith,
On 26/01/16 03:47, Pranith Kumar Karampuri wrote:
hi,
Traditionally gluster has been using ctime/mtime of the
files/dirs on the bricks as stat
Answers inline:
- Original Message -
From: "Joe Julian" <j...@julianfamily.org>
To: gluster-devel@gluster.org
Sent: Tuesday, January 26, 2016 1:45:36 PM
Subject: Re: [Gluster-devel] distributed files/directories and [cm]time updates
If the time is set on a fi
Hi Xavier,
There is a patch sent for review which implements the metadata cache in the
posix layer. What the changes do is this:
Whenever there is a fresh lookup on a object (file/directory/symlink),
posix xlator saves the stat attributes of that object in its cache.
As of now, whenever there
> If the time is set on a file by the client, this increases the critical
> complexity to include the clients whereas before it was only critical to
> have the servers time synced, now the clients should be as well.
With any kind of server-side replication, the times could be generated by
the
Hi Pranith,
On 26/01/16 03:47, Pranith Kumar Karampuri wrote:
hi,
Traditionally gluster has been using ctime/mtime of the
files/dirs on the bricks as stat output. Problem we are seeing with this
approach is that, software which depends on it gets confused when there
are differences in
hi,
Traditionally gluster has been using ctime/mtime of the
files/dirs on the bricks as stat output. Problem we are seeing with this
approach is that, software which depends on it gets confused when there
are differences in these times. Tar especially gives "file changed as we
read it"
11 matches
Mail list logo
