- Original Message -
> From: "Pranith Kumar Karampuri"
> To: "Vijay Bellur"
> Cc: "Gluster Devel"
> Sent: Wednesday, May 28, 2014 4:16:32 PM
> Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for
> setxa
uot;
> > To: "Pranith Kumar Karampuri"
> > Cc: "Kaleb KEITHLEY" , "Gluster Devel"
> >
> > Sent: Friday, May 23, 2014 2:12:02 AM
> > Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for
> > setxattr
> >
> >
essage -
> >>> From: "Kaleb KEITHLEY"
> >>> To: gluster-devel@gluster.org
> >>> Sent: Tuesday, May 13, 2014 8:01:53 PM
> >>> Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for
> >>> setxattr
> >>>
ch to remove the special treatment of ENOTSUP here:
>> http://review.gluster.org/7788
>>
>> Pranith
>> ----- Original Message -
>>> From: "Kaleb KEITHLEY"
>>> To: gluster-devel@gluster.org
>>> Sent: Tuesday, May 13, 2014 8:01:53 PM
>
.gluster.org/7788
>
> Pranith
> - Original Message -
>> From: "Kaleb KEITHLEY"
>> To: gluster-devel@gluster.org
>> Sent: Tuesday, May 13, 2014 8:01:53 PM
>> Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for
>> setxattr
>
Gowdappa"
> >>> To: "Pranith Kumar Karampuri"
> >>> Cc: "Vijay Bellur" , gluster-devel@gluster.org,
> >>> "Anand Avati"
> >>> Sent: Wednesday, May 7, 2014 3:42:16 PM
> >>> Subject: Re: [Gluster-devel]
vati"
Sent: Wednesday, May 7, 2014 3:42:16 PM
Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP
for setxattr
I think with "repetitive log message suppression" patch being merged, we
don't really need gf_log_occasionally (except if they are logged in
DE
quot;Vijay Bellur"
Cc: gluster-devel@gluster.org, "Anand Avati"
Sent: Wednesday, 7 May, 2014 3:12:10 PM
Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for
setxattr
- Original Message -
From: "Vijay Bellur"
To: "Pranith Kumar Karampu
M
Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for setxattr
I think with "repetitive log message suppression" patch being merged, we
don't really need gf_log_occasionally (except if they are logged in DEBUG or
TRACE levels).
That definitely helps. But still, setx
- Original Message -
> From: "Raghavendra Gowdappa"
> To: "Pranith Kumar Karampuri"
> Cc: "Vijay Bellur" , gluster-devel@gluster.org, "Anand
> Avati"
> Sent: Wednesday, May 7, 2014 3:42:16 PM
> Subject: Re: [Gluster-devel] reg
> Cc: gluster-devel@gluster.org, "Anand Avati"
> Sent: Wednesday, 7 May, 2014 3:12:10 PM
> Subject: Re: [Gluster-devel] regarding special treatment of ENOTSUP for
> setxattr
>
>
>
> - Original Message -
> > From: "Vijay Bellur"
> &
- Original Message -
> From: "Vijay Bellur"
> To: "Pranith Kumar Karampuri" , "Anand Avati"
>
> Cc: gluster-devel@gluster.org
> Sent: Tuesday, May 6, 2014 7:16:12 PM
> Subject: Re: [Gluster-devel] regarding special treatment of ENO
On Tue, May 6, 2014 at 12:37 AM, Pranith Kumar Karampuri
wrote:
> hi,
> Why is there occasional logging for ENOTSUP errno when setxattr fails?
>
Do you really have xattr support? why is it logging in the first
place? - it shouldn't ?
--
Religious confuse piety with mere ritual, the virtuous c
On 05/06/2014 01:07 PM, Pranith Kumar Karampuri wrote:
hi,
Why is there occasional logging for ENOTSUP errno when setxattr fails?
In the absence of occasional logging, the log files would be flooded
with this message every time there is a setxattr() call.
-Vijay
14 matches
Mail list logo
