Re: [Gluster-users] Status of the patch!!!

2018-01-31 Thread ABHISHEK PALIWAL
Hi Atin,

Yes, agree that you explained it repeatedly. Even we are getting this issue
very rarely and that is when we are doing repeated reboot of system.

We tried to debug it further but not able to identify in which
situation/rare case it is generating the empty info file which is causing
this issue.

As, you guys working on this to fix, that is why I asked if you guys know
the race condition or root cause of the problem.


Regards,
Abhishek

On Wed, Jan 31, 2018 at 5:43 PM, Atin Mukherjee  wrote:

> I have repeatedly explained this multiple times the way to hit this
> problem is *extremely rare* and until and unless you prove us wrong and
> explain why do you think you can get into this situation often. I still see
> that information is not being made available to us to think through why
> this fix is critical. Also as I mentioned earlier, this piece of change
> touches upon the core store utils code path which need to be thought out
> really well with all the corner cases before pushing the commit.
>
> On Wed, Jan 31, 2018 at 5:32 PM, ABHISHEK PALIWAL  > wrote:
>
>> Hi Team,
>>
>> I am facing one issue which is exactly same as mentioned on the below link
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1408431
>>
>> Also there are some patches available to fix the issue but seems those
>> are not approved and still discussion is going on
>>
>> https://review.gluster.org/#/c/16279/
>>
>> Currently the status is "Abandoned".
>>
>> Could you please let me know what is our plan to release this patch?
>> Please respond as it is important for us.
>>
>>
>> Regards
>> Abhishek Paliwal
>>
>> ___
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
>


-- 




Regards
Abhishek Paliwal
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Status of the patch!!!

2018-01-31 Thread Atin Mukherjee
I have repeatedly explained this multiple times the way to hit this problem
is *extremely rare* and until and unless you prove us wrong and explain why
do you think you can get into this situation often. I still see that
information is not being made available to us to think through why this fix
is critical. Also as I mentioned earlier, this piece of change touches upon
the core store utils code path which need to be thought out really well
with all the corner cases before pushing the commit.

On Wed, Jan 31, 2018 at 5:32 PM, ABHISHEK PALIWAL 
wrote:

> Hi Team,
>
> I am facing one issue which is exactly same as mentioned on the below link
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1408431
>
> Also there are some patches available to fix the issue but seems those are
> not approved and still discussion is going on
>
> https://review.gluster.org/#/c/16279/
>
> Currently the status is "Abandoned".
>
> Could you please let me know what is our plan to release this patch?
> Please respond as it is important for us.
>
>
> Regards
> Abhishek Paliwal
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users