HI Atin
it seems like some spurious fail (failed one time). My patch nothing
to do with snapshot. I will send my patch with rebase .
Regards
Anand.N
On 05/29/2015 07:17 PM, Atin Mukherjee wrote:
Anand,
Could you check if your patch [1] fails this regression every time?
Otherwise I would
Also, good to have this patch in: http://review.gluster.org/#/c/11030/
(waiting for regression to run).
-Venky
On Mon, Jun 1, 2015 at 4:23 PM, Avra Sengupta aseng...@redhat.com wrote:
Aravinda has given it a +1
Regards,
Avra
On 06/01/2015 03:34 PM, Krishnan Parthasarathi wrote:
Could
While looking into some of the races that seem possible in the new
auth-cache and netgroup/export features for Gluster/NFS, I noticed that
we do not really have a common way to do reference counting. I could
really use that, so I've put something together and would like to
request some
- Original Message -
From: Venky Shankar vshan...@redhat.com
To: gg...@redhat.com, anekk...@redhat.com
Cc: gluster-devel@gluster.org
Sent: Monday, June 1, 2015 3:28:21 PM
Subject: Re: [Gluster-devel] scrubber crash
On 06/01/2015 02:23 PM, Venky Shankar wrote:
On 06/01/2015 01:09
Hi Venky
one of regression test in my patch, I found core dump from scrubber
. Please have a look.
Link
:http://build.gluster.org/job/rackspace-regression-2GB-triggered/9925/consoleFull
bt fir core ...
(gdb) bt
#0 0x7f89d6224731 in gf_tw_mod_timer_pending (base=0xf2fbc0,
All,
I will be pushing GlusterFS 3.7.1 release in couple of hours. This release
is to fix BZ 1223215 - gluster volume status fails with locking failed error
message.
If there are other fixes that cause users unacceptable inconvenience, please
get your patches merged by respective maintainers in
On 06/01/2015 02:23 PM, Venky Shankar wrote:
On 06/01/2015 01:09 PM, Anand Nekkunti wrote:
Hi Venky
one of regression test in my patch, I found core dump from
scrubber . Please have a look.
Link
:http://build.gluster.org/job/rackspace-regression-2GB-triggered/9925/consoleFull
bt
On 06/01/2015 01:09 PM, Anand Nekkunti wrote:
Hi Venky
one of regression test in my patch, I found core dump from scrubber
. Please have a look.
Link
:http://build.gluster.org/job/rackspace-regression-2GB-triggered/9925/consoleFull
bt fir core ...
(gdb) bt
#0 0x7f89d6224731 in
Aravinda has given it a +1
Regards,
Avra
On 06/01/2015 03:34 PM, Krishnan Parthasarathi wrote:
Could you get a +1 from Aravinda?
- Original Message -
Hi KP,
Can we have this patch in 3.7.1 before you make the release.
http://review.gluster.org/#/c/10993/
Regards,
Avra
On
(gdb) p *xattr
Cannot access memory at address 0xadc0de7f288c
This indicates a use-after-free problem. The 0xadc0de from *xattr would
be 0xdeadc0de, just a little chopped of. This pattern is written to
the area after GF_FREE() is called on a pointer when compiles with
Sent from Samsung Galaxy S4
On 1 Jun 2015 20:37, Emmanuel Dreyfus m...@netbsd.org wrote:
On Mon, Jun 01, 2015 at 05:07:03AM -0400, Krishnan Parthasarathi wrote:
I will be pushing GlusterFS 3.7.1 release in couple of hours. This
release
is to fix BZ 1223215 - gluster volume status fails with
On Mon, Jun 01, 2015 at 05:07:03AM -0400, Krishnan Parthasarathi wrote:
I will be pushing GlusterFS 3.7.1 release in couple of hours. This release
is to fix BZ 1223215 - gluster volume status fails with locking failed error
message.
Was http://review.gluster.org/10842/ backported to
On Mon, Jun 01, 2015 at 09:13:45PM +0530, Atin Mukherjee wrote:
10959 it is in 3.7 and its backported.
Fine. But there is a missing bug, as the logs are filled by the same message
evey second:
[2015-06-01 16:21:43.049150] W [socket.c:3059:socket_connect] 0-nfs: Ignore
failed connection attempt
On 06/02/2015 10:40 AM, Krishnan Parthasarathi wrote:
ec/self-heal.t failed regression reporting: not ok 71 Got -rw---
instead of -rw-r--r-- (regression had passed with earlier patchset).
Console output is:
http://build.gluster.org/job/rackspace-regression-2GB-triggered/9881/consoleFull
Thank you Emmanuel.
- Original Message -
Krishnan Parthasarathi kpart...@redhat.com wrote:
Yes. 3.7.1 aims to alleviate the volume-status issue as top priority.
We couldn't get the above patch within reasonable time. I will be
backporting it and ensure it makes it to 3.7.2,
Krishnan Parthasarathi kpart...@redhat.com wrote:
Yes. 3.7.1 aims to alleviate the volume-status issue as top priority.
We couldn't get the above patch within reasonable time. I will be
backporting it and ensure it makes it to 3.7.2, expected in two weeks.
3.7.2 should address a wider range
16 matches
Mail list logo
