Re: [Gluster-devel] distributed files/directories and [cm]time updates

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

Re: [Gluster-devel] Smoke tests run on the builder in RH DC (at least)

Le mardi 26 janvier 2016 à 01:42 +0530, Raghavendra Talur a écrit : > On Mon, Jan 25, 2016 at 11:29 PM, Michael Scherer > wrote: > > > Hi, > > > > so today, after fixing one last config item, the smoke test jobs run > > fine on the Centos 6 builder in the RH DC, which build

Re: [Gluster-devel] distributed files/directories and [cm]time updates

Hi Joseph, On 26/01/16 10:42, Joseph Fernandes wrote: Hi Xavi, Answer inline: - Original Message - From: "Xavier Hernandez" To: "Joseph Fernandes" Cc: "Pranith Kumar Karampuri" , "Gluster Devel"

Re: [Gluster-devel] [Gluster-infra] Smoke tests run on the builder in RH DC (at least)

Le mardi 26 janvier 2016 à 09:47 +0100, Niels de Vos a écrit : > On Tue, Jan 26, 2016 at 08:55:39AM +0100, Michael Scherer wrote: > > Le lundi 25 janvier 2016 à 22:24 +0100, Niels de Vos a écrit : > > > On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote: > > > > I was also planning

Re: [Gluster-devel] distributed files/directories and [cm]time updates

Hi Xavi, Answer inline: - Original Message - From: "Xavier Hernandez" To: "Joseph Fernandes" Cc: "Pranith Kumar Karampuri" , "Gluster Devel" Sent: Tuesday, January 26, 2016 2:09:43 PM Subject:

Re: [Gluster-devel] Feature: Automagic lock-revocation for features/locks xlator (v3.7.x)

On Mon, Jan 25, 2016 at 10:39 AM, Raghavendra Gowdappa wrote: > > > - Original Message - > > From: "Richard Wareing" > > To: "Pranith Kumar Karampuri" > > Cc: gluster-devel@gluster.org > > Sent: Monday, January 25, 2016 8:17:11

Re: [Gluster-devel] rm -r problem on FreeBSD port

> However, other times, the "rm" doesn't report an error, but the file remains > visible via "ls" and the rmdir fails. when this case happens does the ls show a linkto file or the original data file. > When I looked at the system calls via ktrace (I'm guessing similar to strace > under Linux?),

Re: [Gluster-devel] [Gluster-users] Determining Connected Client Version

On 01/27/2016 09:21 AM, Atin Mukherjee wrote: On 01/27/2016 07:21 AM, Vijay Bellur wrote: On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: I'm trying to set a parameter on a volume, but unable to due to the following message. I have a large number of connected clients and it's likely that

Re: [Gluster-devel] [Gluster-users] Determining Connected Client Version

On 01/27/2016 12:49 PM, Atin Mukherjee wrote: On 01/27/2016 12:40 PM, Pranith Kumar Karampuri wrote: On 01/27/2016 09:21 AM, Atin Mukherjee wrote: On 01/27/2016 07:21 AM, Vijay Bellur wrote: On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: I'm trying to set a parameter on a volume, but

Re: [Gluster-devel] [Gluster-users] Determining Connected Client Version

On 01/27/2016 07:21 AM, Vijay Bellur wrote: > On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: >> I'm trying to set a parameter on a volume, but unable to due to the >> following message. I have a large number of connected clients and it's >> likely that some clients have updated packages but

Re: [Gluster-devel] patch #10954

Hi, I suppose someone from glusterd team can confirm if the patch #10954 requires a backport to 3.7. Even if a backport is required it would probably be better to first remove brick_up_status() and use just brick_up_status_1() or vice versa (to avoid any further confusion on which function to

Re: [Gluster-devel] patch #10954

On 01/27/2016 11:11 AM, Sakshi Bansal wrote: > Hi, > > I suppose someone from glusterd team can confirm if the patch #10954 requires > a backport to 3.7. If anything is going in mainline I'd encourage the same to be backported irrespective of the severity of the fix, so that's out of the

Re: [Gluster-devel] [Gluster-users] Determining Connected Client Version

On 01/27/2016 12:40 PM, Pranith Kumar Karampuri wrote: > > > On 01/27/2016 09:21 AM, Atin Mukherjee wrote: >> >> On 01/27/2016 07:21 AM, Vijay Bellur wrote: >>> On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: I'm trying to set a parameter on a volume, but unable to due to the

[Gluster-devel] Simple way to re-trigger jenkins jobs

Hi, Prashanth informed about a simple way to let every contributor retrigger the regression runs that openstack uses. We have implemented same for gluster. Trigger comments are: recheck netbsd recheck smoke recheck centos You just have to reply on the patch set with one of the following

Re: [Gluster-devel] [Gluster-infra] Smoke tests run on the builder in RH DC (at least)

On Tue, Jan 26, 2016 at 08:55:39AM +0100, Michael Scherer wrote: > Le lundi 25 janvier 2016 à 22:24 +0100, Niels de Vos a écrit : > > On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote: > > > Hi, > > > > > > so today, after fixing one last config item, the smoke test jobs run > > >

Re: [Gluster-devel] distributed files/directories and [cm]time updates

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. Just spitballing here, but what if the time was converted at the posix layer as a

[Gluster-devel] patch #10954

Hey Sakshi, patch #10954 was not backported to 3.7 (for whatever reason) but introduced a helper routine brick_up_status() in tests/volume.rc. This routine was used in writing test cases for couple of patches http://review.gluster.org/#/c/13120/

Re: [Gluster-devel] distributed files/directories and [cm]time updates

Answer inline: - Original Message - From: "Xavier Hernandez" To: "Pranith Kumar Karampuri" , "Gluster Devel" Sent: Tuesday, January 26, 2016 1:21:37 PM Subject: Re: [Gluster-devel] distributed files/directories and

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" To: "Pranith Kumar Karampuri" , "Gluster Devel" Sent: Tuesday, January 26, 2016 1:21:37 PM

Re: [Gluster-devel] distributed files/directories and [cm]time updates

Answers inline: - Original Message - From: "Joe Julian" 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 file by the client, this

Re: [Gluster-devel] distributed files/directories and [cm]time updates

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

Re: [Gluster-devel] rm -r problem on FreeBSD port

Sakshi Bansal wrote: > I would expect cluster.lookup-optimize to be creating the problem here, so > may be you could first try with this option off. Another thing that would be > helpful is to get the strace when rm fails with no such file, as this would > tell us to identify if the readdir is not

Re: [Gluster-devel] distributed files/directories and [cm]time updates

> 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