> Seems like we are already inside pool->lock while doing statedump which
> does writes to files, so may be I shouldn't think too much :-/. I will
> take a look at your patch once.
Ah, now it makes sense. I thought you knew about pool->lock already.
I was wondering why you were even trying to avoi
On 06/07/2015 05:40 PM, Pranith Kumar Karampuri wrote:
On 06/05/2015 09:10 AM, Krishnan Parthasarathi wrote:
- Original Message -
This seems to happen because of race between STACK_RESET and stack
statedump. Still thinking how to fix it without taking locks around
writing to file.
On 06/05/2015 09:10 AM, Krishnan Parthasarathi wrote:
- Original Message -
This seems to happen because of race between STACK_RESET and stack
statedump. Still thinking how to fix it without taking locks around
writing to file.
Why should we still keep the stack being reset as part of
On 06/05/2015 09:01 AM, Krishnan Parthasarathi wrote:
This seems to happen because of race between STACK_RESET and stack
statedump. Still thinking how to fix it without taking locks around
writing to file.
Why should we still keep the stack being reset as part of pending pool of
frames? Even w
- Original Message -
>
>
> - Original Message -
> >
> > > This seems to happen because of race between STACK_RESET and stack
> > > statedump. Still thinking how to fix it without taking locks around
> > > writing to file.
> >
> > Why should we still keep the stack being reset
- Original Message -
>
> > This seems to happen because of race between STACK_RESET and stack
> > statedump. Still thinking how to fix it without taking locks around
> > writing to file.
>
> Why should we still keep the stack being reset as part of pending pool of
> frames? Even we if w
> This seems to happen because of race between STACK_RESET and stack
> statedump. Still thinking how to fix it without taking locks around
> writing to file.
Why should we still keep the stack being reset as part of pending pool of
frames? Even we if we had to (can't guess why?), when we remove w
This seems to happen because of race between STACK_RESET and stack
statedump. Still thinking how to fix it without taking locks around
writing to file.
Pranith
On 06/04/2015 02:13 PM, Pranith Kumar Karampuri wrote:
I see that statedump is generating core because of which this test
spuriously f
I see that statedump is generating core because of which this test
spuriously fails. I am looking into it.
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
