On 06/08/2015 05:21 PM, Jeff Darcy wrote:
Every resource(thread, mem pools) is associated with glusterfs_ctx,
hence as the ctxs in the process grows the resource utilization also
grows (most of it being unused). This mostly is an issue with any
libgfapi application: USS, NFS Ganesha, Samba,
This patch has passed regression test on Linux and has gotten
CodeReview+2. The NetBSD regression isn't automatically run
on this patch. Is there a way to (re)trigger NetBSD regression
on this patch?
___
Gluster-devel mailing list
On 06/09/2015 09:39 AM, Krishnan Parthasarathi wrote:
This patch has passed regression test on Linux and has gotten
CodeReview+2. The NetBSD regression isn't automatically run
on this patch. Is there a way to (re)trigger NetBSD regression
on this patch?
Re-triggered. Here is what you can do
Re-triggered. Here is what you can do in future:
1. Find out the ref_spec number of patch from the download at the top
right corner of gerrit interface, for eg : refs/changes/29/11129/1.
Please note you would need to copy the ref number for the latest patch set.
2. Log in into
Hi,
As part of Bit-rot detection feature a file that has its data changed
due to some backend errors is marked as a bad file by the scrubber (sets
an extended attribute indicating its a bad file). Now, the access to the
bad file has to be denied (to prevent wrong data being served).
In
- Original Message -
From: Atin Mukherjee amukh...@redhat.com
To: Vijay Bellur vbel...@redhat.com, Gluster Devel
gluster-devel@gluster.org
Cc: Vijaikumar Mallikarjuna vmall...@redhat.com, Sachin Pandit
span...@redhat.com
Sent: Sunday, June 7, 2015 10:25:24 AM
Subject: Re:
On 06/08/2015 01:14 AM, Emmanuel Dreyfus wrote:
Emmanuel Dreyfus m...@netbsd.org wrote:
I will try to craft a change for that tomorrow.
Here it is:
http://review.gluster.org/4
This is untested, I rely on the test suite to find bugs.
Thanks, I was also working on a similar change in
tests/basic/op_errnos.t is now causing problems in regression runs [1].
Rajesh, Avra - can you please take a look?
Thanks,
Vijay
[1]
http://build.gluster.org/job/rackspace-regression-2GB-triggered/10263/consoleFull
___
Gluster-devel mailing list
On Mon, Jun 08, 2015 at 10:32:15AM +0530, Atin Mukherjee wrote:
All the tests are complaining about missing env.rc
The funny thing is that the first tests find it, which means
something removes it duirng the test suite.
And it is not the only removed thing:
The patch @ http://review.gluster.org/#/c/9/ fixes this issue. Review(s)
requested.
-Krutika
- Original Message -
From: Krutika Dhananjay kdhan...@redhat.com
To: Soumya Koduri skod...@redhat.com
Cc: Gluster Devel gluster-devel@gluster.org
Sent: Monday, June 8, 2015 11:38:00 AM
My patch itself has some issue it seems , I am working on that . I
will (re)send my patch once it resolved.
Regards
Anand
On 06/08/2015 04:25 PM, Vijay Bellur wrote:
tests/basic/op_errnos.t is now causing problems in regression runs
[1]. Rajesh, Avra - can you please take a look?
Sent a patch to fix the failure
http://review.gluster.org/#/c/11125/
I will back-port the patch once it gets
merged in the master branch.
Thanks,
Sachin.
- Original Message -
From: Sachin Pandit span...@redhat.com
To: Atin Mukherjee amukh...@redhat.com
Cc: Gluster Devel
On 06/08/2015 05:06 PM, Pranith Kumar Karampuri wrote:
On 06/05/2015 04:01 PM, Anuradha Talur wrote:
gluster volume heal volname info doesn't seem to fail because
the process is crashing in afr_notify when invoked by glfs_fini.
As a result proper error codes are not being propagated.
Looking at it from a different perspective...
As I understand it, the purpose of glusterfs_ctx is to be a container
for these resources. Therefore, the problem is not that the resources
aren't shared within a context but that the contexts aren't shared
among glfs objects. This happens
Yes, this makes sense. I see that there are a few members of
glusterfs_ctx_t(ctx)
that needs to be handled with care. ctx assumes that there is only one volume
being managed in a glusterfs* process. It has only one volfile-server
connection, only one client_t table for connections to a volume
On 06/05/2015 04:01 PM, Anuradha Talur wrote:
gluster volume heal volname info doesn't seem to fail because
the process is crashing in afr_notify when invoked by glfs_fini.
As a result proper error codes are not being propagated.
Pranith had recently sent a patch :
On 06/08/2015 04:57 PM, Anand Nekkunti wrote:
My patch itself has some issue it seems , I am working on that . I
will (re)send my patch once it resolved.
Thanks, Anand!
-Vijay
___
Gluster-devel mailing list
Gluster-devel@gluster.org
comments inline.
- Original Message -
From: Sachin Pandit span...@redhat.com
To: Atin Mukherjee amukh...@redhat.com
Cc: Gluster Devel gluster-devel@gluster.org
Sent: Monday, June 8, 2015 11:40:05 AM
Subject: Re: [Gluster-devel] release-3.7 regression tests stability
-
Every resource(thread, mem pools) is associated with glusterfs_ctx,
hence as the ctxs in the process grows the resource utilization also
grows (most of it being unused). This mostly is an issue with any
libgfapi application: USS, NFS Ganesha, Samba, vdsm, qemu. It is
normal in any of the
19 matches
Mail list logo
