Hi Avra,
Thank you.
Sriram
On Thu, Jan 12, 2017, at 12:40 PM, Avra Sengupta wrote:
> Works fine for us Sriram. Friday 2-3 pm.
>
> Regards,
> Avra
>
> On 01/12/2017 11:54 AM, sri...@marirs.net.in wrote:
>> Hi Avra,
>>
>> Sorry for the late reply, could we have the meeti
On Thu, Jan 12, 2017 at 4:44 PM, Raghavendra G
wrote:
>
>
> On Thu, Jan 12, 2017 at 4:35 PM, Raghavendra G
> wrote:
>
>>
>>
>> On Thu, Jan 12, 2017 at 9:20 AM, B.K.Raghuram wrote:
>>
>>> cc'ing devel as well for some developer insight..
>>>
>>> -- Forwarded message --
>>> To: gl
Xavi,
I changed the logging to log the individual bytes. Consider the
following from ws-glus.log file where /ws/glus is the mount point.
[2017-01-12 20:47:59.368102] I [MSGID: 109063]
[dht-layout.c:718:dht_layout_normalize] 0-glusterfsProd-dht: Found anomalies in
/Folder_01.05.2017
Quite helpful, I definitely feel this to be a good blog material.
On Thu, 12 Jan 2017 at 16:29, Raghavendra Gowdappa
wrote:
> All,
>
>
>
> Not sure many of us know about how to selectively set log-level of an
> xlator. Thought this might be helpful to someone.
>
>
>
> To selectively set log-leve
Hi Ram,
On 12/01/17 11:49, Ankireddypalle Reddy wrote:
Xavi,
As I mentioned before the error could happen for any FOP. Will try to
run with TRACE debug level. Is there a possibility that we are checking for
this attribute on a directory, because a directory does not seem to be havin
On Thu, Jan 12, 2017 at 4:35 PM, Raghavendra G
wrote:
>
>
> On Thu, Jan 12, 2017 at 9:20 AM, B.K.Raghuram wrote:
>
>> cc'ing devel as well for some developer insight..
>>
>> -- Forwarded message --
>> To: gluster-users
>>
>>
>> I had a question on the expected behaviour of simpl
On Thu, Jan 12, 2017 at 9:20 AM, B.K.Raghuram wrote:
> cc'ing devel as well for some developer insight..
>
> -- Forwarded message --
> To: gluster-users
>
>
> I had a question on the expected behaviour of simple distributed volumes
> when a brick fails for the following scenarios
All,
Not sure many of us know about how to selectively set log-level of an xlator.
Thought this might be helpful to someone.
To selectively set log-level of an xlator we need to do setfattr on any path in
glusterfs with "trusted.glusterfs.%s.set-log-level" (where %s is name of xlator
in xlator
Xavi,
As I mentioned before the error could happen for any FOP. Will try to
run with TRACE debug level. Is there a possibility that we are checking for
this attribute on a directory, because a directory does not seem to be having
this attribute set. Also is the function to check size a
