On 05/07/2014 03:44 PM, Pranith Kumar Karampuri wrote:
----- Original Message -----
From: "Raghavendra Gowdappa" <rgowdapp@xxxxxxxxxx>
To: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx>
Cc: "Vijay Bellur" <vbellur@xxxxxxxxxx>, gluster-devel@xxxxxxxxxxx, "Anand Avati" <aavati@xxxxxxxxxx>
Sent: Wednesday, May 7, 2014 3:42:16 PM
Subject: Re: 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
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
