On Sat, Sep 13, 2014 at 01:34:58PM -0700, Anand Avati wrote:
How does the NetBSD nfs server provide stable directory offsets, for the
NFS client to resume reading from at a later point in time? Very similar
problems are present in that scenario and it might be helpful to see what
approaches
On 09/18/2014 03:13 PM, Niels de Vos wrote:
On Thu, Sep 18, 2014 at 07:43:00AM +0530, Pranith Kumar Karampuri wrote:
hi,
Till now the only method I used to find ref leaks effectively is to find
what operation is causing ref leaks and read the code to find if there is a
ref-leak somewhere.
hi,
how can i stop a brick ? because that brick need check file system, need a
long time, so i need stop it, and start it when repair finish.
thank you
everybody_en...@163.com
___
Gluster-devel mailing list
Gluster-devel@gluster.org
On Thu, Sep 18, 2014 at 05:42:01PM +0530, Humble Devassy Chirammal wrote:
As decided in our last GlusterFS meeting and the 3.6 planning schedule, we
shall conduct GlusterFS 3.6 test days starting from next week.
I still have a few portability fixes pending in gerrit for NetBSD. Do we
plan to
On 09/18/2014 06:07 PM, Emmanuel Dreyfus wrote:
On Thu, Sep 18, 2014 at 05:42:01PM +0530, Humble Devassy Chirammal wrote:
As decided in our last GlusterFS meeting and the 3.6 planning schedule, we
shall conduct GlusterFS 3.6 test days starting from next week.
I still have a few portability
On 09/17/2014 10:13 PM, Pranith Kumar Karampuri wrote:
hi,
Till now the only method I used to find ref leaks effectively is to
find what operation is causing ref leaks and read the code to find if
there is a ref-leak somewhere. Valgrind doesn't solve this problem
because it is reachable
On 09/18/2014 07:48 PM, Shyam wrote:
On 09/17/2014 10:13 PM, Pranith Kumar Karampuri wrote:
hi,
Till now the only method I used to find ref leaks effectively is to
find what operation is causing ref leaks and read the code to find if
there is a ref-leak somewhere. Valgrind doesn't solve
If we could disable/enable ref tracking dynamically, it may only be heavy
weight tempoarily while the customer is being observed.
You could get a state dump , or another idea is to take a core of the live
process. gcore $(pidof processname)
- Original Message -
From: Pranith Kumar
As a wishlist item, I think it'd be nice if debug builds (or some other
build-time option) would disable the pools. Then valgrind might be more
useful for finding leaks.
Maybe for GlusterFS-4.0?
On 09/18/2014 11:40 AM, Dan Lambright wrote:
If we could disable/enable ref tracking
On 09/18/2014 09:31 PM, Kaleb KEITHLEY wrote:
As a wishlist item, I think it'd be nice if debug builds (or some
other build-time option) would disable the pools. Then valgrind might
be more useful for finding leaks.
Maybe for GlusterFS-4.0?
This is already available
I am going to be bold and throw a suggestion inspired from
what I read today. I was reading briefly about how kernel
manages its objects using the kobject data structure and
establishe 'liveness' (in the garbage collection sense)
relationship across objects. It allows one to group objects
into
On 09/18/2014 12:09 PM, Pranith Kumar Karampuri wrote:
On 09/18/2014 09:35 PM, Pranith Kumar Karampuri wrote:
On 09/18/2014 09:31 PM, Kaleb KEITHLEY wrote:
As a wishlist item, I think it'd be nice if debug builds (or some
other build-time option) would disable the pools. Then valgrind might
12 matches
Mail list logo
