Nobody has an idea on this one?
This is master branch, client side:
Program terminated with signal 11, Segmentation fault.
#0 uuid_unpack (in=0xffc0 Address 0xffc0 out of bounds,
uu=0xbf7fd7b0) at ../../contrib/uuid/unpack.c:43
warning: Source file is more recent than
Hi Emmanuel,
Is it possible to get valgrind reports (or a test case which caused this
crash)? The inode table is corrupted in this case.
regards,
Raghavendra
- Original Message -
From: Emmanuel Dreyfus m...@netbsd.org
To: gluster-devel@gluster.org
Sent: Wednesday, May 21, 2014
On 05/21/2014 11:42 AM, Atin Mukherjee wrote:
On 05/21/2014 10:54 AM, SATHEESARAN wrote:
Guys,
This is the issue pointed out by Pranith with regard to Barrier.
I was reading through it.
But I wanted to bring it to concern
-- S
Original Message
Subject: Re:
- Original Message -
From: Atin Mukherjee amukh...@redhat.com
To: gluster-devel@gluster.org, Pranith Kumar Karampuri pkara...@redhat.com
Sent: Wednesday, May 21, 2014 3:39:21 PM
Subject: Re: Fwd: Re: [Gluster-devel] Spurious failures because of nfs and
snapshots
On
On Wed, 21 May 2014 00:06:22 -0700
Anand Avati av...@gluster.org wrote:
On Tue, May 20, 2014 at 10:54 PM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
- Original Message -
From: Anand Avati av...@gluster.org
To: Pranith Kumar Karampuri pkara...@redhat.com
Cc:
- Original Message -
From: Anand Avati av...@gluster.org
To: Pranith Kumar Karampuri pkara...@redhat.com
Cc: Edward Shishkin edw...@redhat.com, Gluster Devel
gluster-devel@gluster.org
Sent: Wednesday, May 21, 2014 12:36:22 PM
Subject: Re: [Gluster-devel] spurios failures in
Hi All,
We realised ( Humble, Niels and I) that we dont have any documentation
regarding the $sub, while disscussing over a backport in #gluster-dev.
The below[1] wiki page is a result of this. Comments, feedbacks are welcome.
[1]
Reminder!!!
The weekly Gluster Community meeting is in 3 mins, in
#gluster-meeting on IRC.
This is a completely public meeting, everyone is encouraged
to attend and be a part of it. :)
To add Agenda items
***
Just add them to the main text of the Etherpad, and be at
the
KP, Atin and myself did some debugging and found that there was a
deadlock in glusterd.
When creating a volume snapshot, the back-end operation 'taking a
lvm_snapshot and starting brick' for the each brick
are executed in parallel using synctask framework.
brick_start was releasing a
On 21/05/2014, at 3:57 PM, Justin Clift wrote:
Reminder!!!
The weekly Gluster Community meeting is in 3 mins, in
#gluster-meeting on IRC.
This is a completely public meeting, everyone is encouraged
to attend and be a part of it. :)
Thanks to everyone for attending this meeting. :)
(1hr
A lot of work has been done on getting blockers resolved for the next
3.5 release. We're not there yet, but we're definitely getting close to
releasing a 1st beta.
Humble will follow-up with an email related to the documentation that is
still missing for features introduced with 3.5. We will
Raghavendra Gowdappa rgowd...@redhat.com wrote:
Is it possible to get valgrind reports
Still no valgrind for NetBSD
(or a test case which caused this crash)?
It happens after some time, but I have no way
to reproduce it quickly.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
Hi all,
Kicked off 21 VM's in Rackspace earlier today, running the regression tests
against master branch.
Only 3 VM's failed out of the 21 (86% PASS, 14% FAIL), with all three being
for the same test:
Test Summary Report
---
./tests/bugs/bug-948686.t
On 02/17/2014 06:22 PM, Vijay Bellur wrote:
On 02/17/2014 05:11 PM, Alex Pyrgiotis wrote:
On 02/10/2014 07:06 PM, Vijay Bellur wrote:
On 02/05/2014 04:10 PM, Alex Pyrgiotis wrote:
Hi all,
Just wondering, do we have any news on that?
Hi Alex,
I have started some work on this. The progress
hi Raghavendra,
The failures are happening because rebalance status command is failing. I
could see the following logs in glusterd log if I start it with -L DEBUG and
try to recreate the bug. Could you please take a look at it.
Test Summary Report
---
tests/bugs/bug-884455.t
- Original Message -
From: Pranith Kumar Karampuri pkara...@redhat.com
To: Justin Clift jus...@gluster.org
Cc: Gluster Devel gluster-devel@gluster.org
Sent: Thursday, May 22, 2014 6:23:16 AM
Subject: Re: [Gluster-devel] Regression testing results for master branch
-
hi,
I think we should run the regression tests with DEBUG builds so that
GF_ASSERTs are caught. I will work with Justin to make sure we don't see too
many failures before turning it on. I also want the regression tests to catch
memory-corruption (invalid read/write of deallocated memory).
On 05/22/2014 08:37 AM, Pranith Kumar Karampuri wrote:
hi,
I think we should run the regression tests with DEBUG builds so that
GF_ASSERTs are caught.
Excellent idea!, lets do it asap.
I will work with Justin to make sure we don't see too many failures before
turning it on. I also want
18 matches
Mail list logo
