[Bugs] [Bug 1192832] New: log files get flooded when removexattr() can't find a specified key or value
bugzilla at redhat.com
bugzilla at redhat.com
Sun Feb 15 18:47:37 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1192832
Bug ID: 1192832
Summary: log files get flooded when removexattr() can't find a
specified key or value
Product: GlusterFS
Version: 3.5.3
Component: logging
Assignee: bugs at gluster.org
Reporter: vbellur at redhat.com
CC: bernhard.glomm at ecologic.eu, bugs at gluster.org,
gluster-bugs at redhat.com, ndevos at redhat.com
Depends On: 1144527
Blocks: 1188064
+++ This bug was initially created as a clone of Bug #1144527 +++
Description of problem:
I'm running
#: glusterfs -V
#: glusterfs 3.4.5 built on Aug 6 2014 19:15:07
on ubuntu 14.04 from the semiosis ppa
I have a replica 2 with 2 servers.
another client does a fuse mount of a volume.
On rsyncing a bit of data onto the fuse mount,
I get an entry like the below one on the client - for each file that is copied
onto the volume
[2014-09-19 07:57:39.877806] W
[client-rpc-fops.c:1232:client3_3_removexattr_cbk] 0-<volume_name>-client-0:
remote operation failed: No data available
[2014-09-19 07:57:39.877963] W
[client-rpc-fops.c:1232:client3_3_removexattr_cbk] 0-<volume_name>-client-1:
remote operation failed: No data available
[2014-09-19 07:57:39.878462] W [fuse-bridge.c:1172:fuse_err_cbk]
0-glusterfs-fuse: 21741144: REMOVEXATTR()
/<path_to_file>/.<file_name_with_a_leading_dot> => -1 (No data available)
The data itself is present and accessible on the volume and on both bricks.
So three questions:
a.) what kind of data is not available? what is the client complaining about?
b.) since it is a warning and the data seems to be okay - is there anything I
need to fix?
c.) How can I get rid of the amount of log lines? it's more than 3GB/day..
Version-Release number of selected component (if applicable):
glusterfs 3.4.5 built on Aug 6 2014 19:15:07
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
an - so far unknown - xattribute key or value that should be removed couldn't
be found for a specific file
Expected results:
As it is a warning message and the data SEEMS to be okay
logging of this event should be reduced by a meaningful algory like:
if message density bigger than X;print short version.
Additional info:
bricks are running on zol, not xfs
--- Additional comment from Anand Avati on 2014-09-19 12:45:12 EDT ---
REVIEW: http://review.gluster.org/8781 (protocol: Log ENODATA & ENOATTR logs at
DEBUG loglevel in removexattr_cbk.) posted (#4) for review on master by Vijay
Bellur (vbellur at redhat.com)
--- Additional comment from Anand Avati on 2014-09-24 03:49:03 EDT ---
COMMIT: http://review.gluster.org/8781 committed in master by Vijay Bellur
(vbellur at redhat.com)
------
commit bd592f8b8379087604f35c3b377f6e94b9e1697d
Author: Vijay Bellur <vbellur at redhat.com>
Date: Fri Sep 19 19:08:05 2014 +0530
protocol: Log ENODATA & ENOATTR logs at DEBUG loglevel in removexattr_cbk.
Prevents messages of the following type from being seen by default in the
log files:
[2014-09-19 07:57:39.877806] W
[client-rpc-fops.c:1232:client3_3_removexattr_cbk]
0-<volume_name>-client-0:
remote operation failed: No data available
[2014-09-19 07:57:39.877963] W
[client-rpc-fops.c:1232:client3_3_removexattr_cbk]
0-<volume_name>-client-1:
remote operation failed: No data available
Change-Id: I3b1a121b0fc272eb772547275bb8085ed19db5a1
BUG: 1144527
Signed-off-by: Vijay Bellur <vbellur at redhat.com>
Reviewed-on: http://review.gluster.org/8781
Reviewed-by: Niels de Vos <ndevos at redhat.com>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1144527
[Bug 1144527] log files get flooded when removexattr() can't find a
specified key or value
https://bugzilla.redhat.com/show_bug.cgi?id=1188064
[Bug 1188064] log files get flooded when removexattr() can't find a
specified key or value
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list