Re: [Gluster-devel] ./tests/bugs/changelog/bug-1208470.t failed NetBSD

On Tue, Jan 19, 2016 at 09:38:19AM +0530, Ravishankar N wrote: > ./tests/bugs/changelog/bug-1208470.t seems to have failed a NetBSD run: > https://build.gluster.org/job/rackspace-regression-2GB-triggered/17651/consoleFull > Not sure if it is spurious as it passed in the subsequent run. Please

Re: [Gluster-devel] ./tests/bugs/changelog/bug-1208470.t failed NetBSD

On 01/19/2016 02:00 PM, Pranith Kumar Karampuri wrote: On 01/19/2016 01:57 PM, Emmanuel Dreyfus wrote: On Tue, Jan 19, 2016 at 09:38:19AM +0530, Ravishankar N wrote: ./tests/bugs/changelog/bug-1208470.t seems to have failed a NetBSD run:

[Gluster-devel] Documentation @ readthedocs.org - search broken

Hi List, for me it seems the documentation is somewhat broken at them moment. If you go to https://gluster.readthedocs.org/en/latest/ an search for "sharding" you get 3 links. All links are broken: "SORRY - This page does not exist yet" If you search for something in Google (e.g. "glusters

Re: [Gluster-devel] ./tests/bugs/changelog/bug-1208470.t failed NetBSD

Saravanakumar Arumugam wrote: Hi, Yes, I can easily add additional 2 second sleep. But, the problem here is: irrespective of anything(especially these timing changes), it should not create any additional changelog. It is a test volume created for test purpose where no I/O is carried out. So,

[Gluster-devel] REMINDER: Gluster Community Bug Triage meeting (Today)

Hi all, The weekly bug triage is about to take place in ~120 minutes. Meeting details: - location: #gluster-meeting on Freenode IRC ( https://webchat.freenode.net/?channels=gluster-meeting ) - date: every Tuesday - time: 12:00 UTC (in your terminal, run: date -d "12:00

[Gluster-devel] Linux regression tests are hanging too

Result: PASS Build timed out (after 300 minutes). Marking the build as failed. Build was aborted Finished: FAILURE https://build.gluster.org/job/rackspace-regression-2GB-triggered/17664/console Pranith ___ Gluster-devel mailing list

Re: [Gluster-devel] How to cope with spurious regression failures

On 01/19/2016 10:45 AM, Emmanuel Dreyfus wrote: > Hi > > Spurious regression failures make developers frustrated. One submits a > change and gets completely unrelated failures. The only way out is to > retrigger regression until it passes, a boring and time-wasting task. > Sometimes after 4 or

Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage

- Original Message - > From: "Martin Simmons" > To: "Raghavendra Gowdappa" > Cc: rmack...@uoguelph.ca, jda...@redhat.com, raghaven...@gluster.com, > gluster-devel@gluster.org, > freebsd...@freebsd.org, xhernan...@datalab.es,

Re: [Gluster-devel] Linux regression tests are hanging too

On Tue, Jan 19, 2016 at 5:20 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > Result: PASS > Build timed out (after 300 minutes). Marking the build as failed. > Build was aborted > Finished: FAILURE > > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/17664/console >

Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage

Raghavendra Gowdappa wrote: > > > - Original Message - > > From: "Rick Macklem" > > To: "Raghavendra Gowdappa" > > Cc: "Jeff Darcy" , "Raghavendra G" > > , "freebsd-fs" > > ,

Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage

Raghavendra Gowdappa wrote: > > > - Original Message - > > From: "Martin Simmons" > > To: "Raghavendra Gowdappa" > > Cc: rmack...@uoguelph.ca, jda...@redhat.com, raghaven...@gluster.com, > > gluster-devel@gluster.org, > >

Re: [Gluster-devel] [Gluster-users] Memory leak in GlusterFS FUSE client

Here is another RAM usage stats and statedump of GlusterFS mount approaching to just another OOM: === root 32495 1.4 88.3 4943868 1697316 ? Ssl Jan13 129:18 /usr/sbin/ glusterfs --volfile-server=server.example.com --volfile-id=volume /mnt/volume ===

Re: [Gluster-devel] [Gluster-users] Memory leak in GlusterFS FUSE client

And another statedump of FUSE mount client consuming more than 7 GiB of RAM: https://gist.github.com/136d7c49193c798b3ade DHT-related leak? On середа, 13 січня 2016 р. 16:26:59 EET Soumya Koduri wrote: > On 01/13/2016 04:08 PM, Soumya Koduri wrote: > > On 01/12/2016 12:46 PM, Oleksandr

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

Sakshi Bansai wrote: > Hi Rick, > > Could you get us some more information about your setup: > First off, just to make it clear, the setup is a simple 2 brick distribute (no replication or ...) like the doc recommends for a quick tryout. > 1) Are you parallely doing 'rm -r' from multiple mount

Re: [Gluster-devel] [Gluster-users] 3.8 Plan changes - proposal

On 01/19/2016 10:36 PM, Bishoy Mikhael wrote: So what about IPv6?! We are still tracking this for 3.8. The patch which provides this support does look good and after some more reviews I expect it to land in time for 3.8. Regards, Vijay On Tuesday, January 19, 2016, Vijay Bellur

Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage

Raghavendra Gowdappa wrote: > > > - Original Message - > > From: "Martin Simmons" > > To: "Raghavendra Gowdappa" > > Cc: rmack...@uoguelph.ca, jda...@redhat.com, raghaven...@gluster.com, > > gluster-devel@gluster.org, > >

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

- Original Message - From: "Sakshi Bansal" To: "Rick Macklem" Cc: "rhs-zteam" Sent: Wednesday, January 20, 2016 11:34:17 AM Subject: Re: [Gluster-devel] rm -r problem on FreeBSD port Another info that would help is an

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

> Sometimes. When this occurs (I get something like this every time I do an "rm > -r") > I can sometimes go into the directory and do an explicit "rm ". At that > point > it will report that the file doesn't exist (I suspect because it sees 2 of > them and > the second one is gone once the

Re: [Gluster-devel] [Gluster-users] 3.8 Plan changes - proposal

On 01/11/2016 04:22 PM, Vijay Bellur wrote: Hi All, We discussed the following proposal for 3.8 in the maintainers mailing list and there was general consensus about the changes being a step in the right direction. Would like to hear your thoughts about the same. Changes to 3.8 Plan:

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

Sakshi Bansal wrote: > > > Sometimes. When this occurs (I get something like this every time I do an > > "rm -r") > > I can sometimes go into the directory and do an explicit "rm ". At > > that point > > it will report that the file doesn't exist (I suspect because it sees 2 of > > them and > >

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

The directory deletion is failing with ENOTEMPTY since not all the files inside it have been deleted. Looks like lookup is not listing all the files. It is possible that cluster.lookup-optimize could be the culprit here. When did you turn this option 'on'? Was it during the untaring of the

[Gluster-devel] 3.7.7 update

https://public.pad.fsfe.org/p/glusterfs-3.7.7 is the final list of patches I am waiting for before making 3.7.7 release. Please let me know if I need to wait for any other patches. It would be great if we make the tag tomorrow. Pranith ___

[Gluster-devel] MINUTES of Gluster Community Bug Triage meeting (Today)

Hi All, The minutes of the Gluster community bug triage meeting: Minutes: http://meetbot.fedoraproject.org/gluster-meeting/2016-01-19/gluster_bug_triage.2016-01-19-12.00.html Minutes (text): http://meetbot.fedoraproject.org/gluster-meeting/2016-01-19/gluster_bug_triage.2016-01-19-12.00.txt

Re: [Gluster-devel] How to cope with spurious regression failures

On Tue, Jan 19, 2016 at 5:21 PM, Atin Mukherjee wrote: > > > On 01/19/2016 10:45 AM, Emmanuel Dreyfus wrote: > > Hi > > > > Spurious regression failures make developers frustrated. One submits a > > change and gets completely unrelated failures. The only way out is to > >

[Gluster-devel] Reverse brick order in tier volume- Why?

Hello, When you perform a tier-attach, why are the bricks attached in the reverse order? For example: #gluster v create testvol replica 3 127.0.0.2:/home/ravi/bricks/brick{1..3} force #gluster volume tier testvol attach replica 3

Re: [Gluster-devel] How to cope with spurious regression failures

On 01/19/2016 07:08 PM, Raghavendra Talur wrote: > > > On Tue, Jan 19, 2016 at 5:21 PM, Atin Mukherjee > wrote: > > > > On 01/19/2016 10:45 AM, Emmanuel Dreyfus wrote: > > Hi > > > > Spurious regression failures make

Re: [Gluster-devel] How to cope with spurious regression failures

On Tue, Jan 19, 2016 at 07:08:03PM +0530, Raghavendra Talur wrote: > a. Allowing re-running to tests to make them pass leads to complacency with > how tests are written. > b. A test is bad if it is not deterministic and running a bad test has *no* > value. We are wasting time even if the test runs

[Gluster-devel] NSR: Suggestions for a new name

Hi, The leader election based replication has been called NSR or "New Style Replication" for a while now. We would like to have a new name for the same that's less generic. It can be something like "Leader Driven Replication" or something more specific that would make sense a few years down