Re: [Gluster-devel] This looks like an interesting Gerrit option we could turn on

> > label.Label-Name.copyAllScoresOnTrivialRebase > > > > If true, all scores for the label are copied forward when a new patch > > set is uploaded that is a trivial rebase. A new patch set is considered > > as trivial rebase if the commit message is the same as in the previous > > patch set and i

Re: [Gluster-devel] Rebalance improvement design

Hi Ben, Yes we were using pure dist volume. Will check in to your systems for more info. Can you please update which patch set you used ? In the mean time I will do one set of test with the same configuration on a small data set. Thanks, Susant - Original Message - > From: "Benjami

Re: [Gluster-devel] 3.7 bugs need a clone from mainline?

On 04/29/2015 11:55 AM, Atin Mukherjee wrote: I've seen few cases where we are using mainline bugs in submitting patches in 3.7 release. Process wise this looks incorrect to me. IIRC, earlier the smoke used to complaint about it, but I am not seeing that either these days. Any recent changes on

[Gluster-devel] 3.7 bugs need a clone from mainline?

I've seen few cases where we are using mainline bugs in submitting patches in 3.7 release. Process wise this looks incorrect to me. IIRC, earlier the smoke used to complaint about it, but I am not seeing that either these days. Any recent changes on this? IMO, we should clone all the mainline bugs

[Gluster-devel] Fwd: FSync tester

Hello All, I was comparing the performance of different GlusterFS clients with each other and came across an interesting result. I used fsync tester utility ( here or here ) which basically writes 1MB to

Re: [Gluster-devel] This looks like an interesting Gerrit option we could turn on

On 04/28/2015 10:40 PM, Niels de Vos wrote: > On Tue, Apr 28, 2015 at 05:56:56PM +0100, Justin Clift wrote: >> This sounds like it might be useful for us: >> >> >> https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/config-labels.html#label_copyAllScoresOnTrivialRebase > >

Re: [Gluster-devel] glusterfs blocked.

> I add some private function in dht_create() as bellow. > > When current pwd is not "/",everything is ok,otherwise,syncop_getxattr will > be blocked(In target subvol,"server3_3_getxatt" did not run ). > > > dict_t *xattr = NULL; > loc_t loc = {0, }; > memset (loc.gfid, 0, 16); > loc.gfid[15] =

Re: [Gluster-devel] Rebalance improvement design

Hi Ben, Is it ok if we take a look at your systems? Regards, Nithya - Original Message - From: "Benjamin Turner" To: "Nithya Balachandran" Cc: "Susant Palai" , "Gluster Devel" Sent: Wednesday, 29 April, 2015 2:13:05 AM Subject: Re: [Gluster-devel] Rebalance improvement design I am n

Re: [Gluster-devel] Rebalance improvement design

I am not seeing the performance you were. I am running on 500GB of data: [root@gqas001 ~]# gluster v rebalance testvol status Node Rebalanced-files size scanned failures skipped status run time in secs

Re: [Gluster-devel] This looks like an interesting Gerrit option we could turn on

On 04/28/2015 10:55 PM, Shyam wrote: On 04/28/2015 01:10 PM, Niels de Vos wrote: On Tue, Apr 28, 2015 at 05:56:56PM +0100, Justin Clift wrote: This sounds like it might be useful for us: https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/config-labels.html#label_copyAllSc

Re: [Gluster-devel] This looks like an interesting Gerrit option we could turn on

On 04/28/2015 01:10 PM, Niels de Vos wrote: On Tue, Apr 28, 2015 at 05:56:56PM +0100, Justin Clift wrote: This sounds like it might be useful for us: https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/config-labels.html#label_copyAllScoresOnTrivialRebase label.Label

Re: [Gluster-devel] This looks like an interesting Gerrit option we could turn on

On Tue, Apr 28, 2015 at 05:56:56PM +0100, Justin Clift wrote: > This sounds like it might be useful for us: > > > https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/config-labels.html#label_copyAllScoresOnTrivialRebase label.Label-Name.copyAllScoresOnTrivialRebase If tr

[Gluster-devel] This looks like an interesting Gerrit option we could turn on

This sounds like it might be useful for us: https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/config-labels.html#label_copyAllScoresOnTrivialRebase Yes/no/? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petaby

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

Posted changes for review, https://review.gluster.org/10425 https://review.gluster.org/10426 ~kaushal On Tue, Apr 28, 2015 at 6:34 PM, Kaushal M wrote: > After a long discussion (not really), we've concluded that a 64-bit > uint is really overkill for how we are using the generation number, > an

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

After a long discussion (not really), we've concluded that a 64-bit uint is really overkill for how we are using the generation number, and I'll change it to a 32-bit uint. I'll send a change to do this right away. The generation number we use is not permanent, it is valid only within a GlusterD p

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On 04/28/2015 06:08 PM, Vijay Bellur wrote: > On 04/28/2015 05:48 PM, Kaushal M wrote: >> AFAIU we've not officially supported 32-bit architectures for sometime >> (possibly for ever) as a community. But we had users running it >> anyway. >> >> 3.7 as it is currently, cannot run on 32-bit platfor

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On Tue, Apr 28, 2015 at 06:08:45PM +0530, Vijay Bellur wrote: > Let us retain support for 32-bit platforms. Though as developers we do not > run many tests on non 64-bit platforms, it would be not be good to break > compatibility for 32-bit platforms as we have many community users running > this

[Gluster-devel] Meeting minutes of todays Gluster Community Bug Triage meeting

On Tue, Apr 28, 2015 at 12:58:24PM +0200, Niels de Vos wrote: > > Hi all, > > This meeting is scheduled for anyone that is interested in lssisting > with, or learning more about Bug Triage. > > Meeting details: > - location: #gluster-meeting on Freenode IRC > ( https://webchat.freeno

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On Tue, Apr 28, 2015 at 05:15:30PM +0530, Kaushal M wrote: > Because of this CAA_BITS_PER_LONG is set to 32 and the case for size 8 > isn't compiled in uatomic_add_return. Even though the underlying > (virtual) hardware has 64-bit support, and supports the required > 8-byte wide instrcution, it can

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On 04/28/2015 05:48 PM, Kaushal M wrote: AFAIU we've not officially supported 32-bit architectures for sometime (possibly for ever) as a community. But we had users running it anyway. 3.7 as it is currently, cannot run on 32-bit platforms. I've used atomic operations which depend on specific pro

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

No Raspberry Pi servers any more? On April 28, 2015 5:07:06 AM PDT, Justin Clift wrote: >Does this mean we're officially no longer supporting 32 bit >architectures? > >(or is that just on x86?) > >+ Justin > > >On 28 Apr 2015, at 12:45, Kaushal M wrote: >> Found the problem. The NetBSD slaves a

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

AFAIU we've not officially supported 32-bit architectures for sometime (possibly for ever) as a community. But we had users running it anyway. 3.7 as it is currently, cannot run on 32-bit platforms. I've used atomic operations which depend on specific processor instructions, to increment a 64-bit

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

Does this mean we're officially no longer supporting 32 bit architectures? (or is that just on x86?) + Justin On 28 Apr 2015, at 12:45, Kaushal M wrote: > Found the problem. The NetBSD slaves are running a 32-bit kernel and > userspace. > ``` > nbslave7a# uname -p > i386 > ``` > > Because of

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

Found the problem. The NetBSD slaves are running a 32-bit kernel and userspace. ``` nbslave7a# uname -p i386 ``` Because of this CAA_BITS_PER_LONG is set to 32 and the case for size 8 isn't compiled in uatomic_add_return. Even though the underlying (virtual) hardware has 64-bit support, and suppor

[Gluster-devel] glusterfs blocked.

Hi, I add some private function in dht_create() as bellow. When current pwd is not "/",everything is ok,otherwise,syncop_getxattr will be blocked(In target subvol,"server3_3_getxatt" did not run ). dict_t *xattr = NULL; loc_t loc = {0, }; memset (loc.gfid, 0, 16);

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

I seem to have found the issue. The uatomic_add_return function is defined in urcu/uatomic.h as ``` /* uatomic_add_return */ static inline __attribute__((always_inline)) unsigned long __uatomic_add_return(void *addr, unsigned long val, int len) { switch (len

[Gluster-devel] REMINDER: Gluster Community Bug Triage meeting today at 12:00 UTC (in ~1 hour)

Hi all, This meeting is scheduled for anyone that is interested in lssisting with, or learning more about Bug Triage. Meeting details: - location: #gluster-meeting on Freenode IRC ( https://webchat.freenode.net/?channels=gluster-meeting ) - date: every Tuesday - time: 12:00 UTC

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On 04/28/2015 01:40 PM, Emmanuel Dreyfus wrote: On Tue, Apr 28, 2015 at 01:37:42PM +0530, Anand Nekkunti wrote: __asm__ is for to write assembly code in c (gcc), __volatile__(:::) compiler level barrier to force the compiler not to do reorder the instructions(to avoid optimization ) .

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On 04/28/2015 01:24 PM, Emmanuel Dreyfus wrote: > On Tue, Apr 28, 2015 at 12:15:11PM +0530, Atin Mukherjee wrote: >> I see netbsd regression doesn't execute peer probe from any other tests >> apart from mgmt_v3-locks.t, if it had that would have also failed. So >> the conclusion is peer probe doe

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On Tue, Apr 28, 2015 at 12:15:11PM +0530, Atin Mukherjee wrote: > I see netbsd regression doesn't execute peer probe from any other tests > apart from mgmt_v3-locks.t, if it had that would have also failed. So > the conclusion is peer probe doesn't work in netbsd. It does not work anymore: that wo

Re: [Gluster-devel] Update on mgmt_v3-locks.t failure in netbsd

On Tue, Apr 28, 2015 at 12:15:11PM +0530, Atin Mukherjee wrote: > I see netbsd regression doesn't execute peer probe from any other tests > apart from mgmt_v3-locks.t, if it had that would have also failed. So > the conclusion is peer probe doesn't work in netbsd. Glusterd crashes > with following