[Gluster-devel] regarding special treatment of ENOTSUP for setxattr

Ric Wheeler rwheeler at redhat.com
Tue May 13 11:15:05 UTC 2014


On 05/07/2014 03:44 PM, Pranith Kumar Karampuri wrote:
>
> ----- Original Message -----
>> From: "Raghavendra Gowdappa" <rgowdapp at redhat.com>
>> To: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
>> Cc: "Vijay Bellur" <vbellur at redhat.com>, gluster-devel at gluster.org, "Anand Avati" <aavati at redhat.com>
>> 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 DEBUG or
>> TRACE levels).
> That definitely helps. But still, setxattr calls are not supposed to fail with ENOTSUP on FS where we support gluster. If there are special keys which fail with ENOTSUPP, we can conditionally log setxattr failures only when the key is something new?
>
> Pranith
>

Have we look at the low level log files and/or kernel code to see when we would 
get an error back?  I wonder if we have bumped into a limit somewhere?

Ric




More information about the Gluster-devel mailing list