From bf8e604e35ff5aafd15dd235bf2b565e8cd65ea5 Mon Sep 17 00:00:00 2001 From: Niels de Vos Date: Sat, 25 Jul 2015 10:28:11 +0200 Subject: logging: client3_3_removexattr_cbk should not log expected ENODATA Commit 379dbbfd changed the log level of an expected error message from GF_LOG_DEBUG to '0'. This causes the message to always get logged. It is intended to log the warning when the xattr could not be removed (but exists), removing a non-existing xattr is sufficient as debug. BUG: 1246736 Change-Id: If11d15d699e8152cc32e0c0c1d65b587c5c48892 Signed-off-by: Niels de Vos Reviewed-on: http://review.gluster.org/11759 Tested-by: Gluster Build System Reviewed-by: Joe Julian Tested-by: Joe Julian Tested-by: NetBSD Build System --- xlators/protocol/client/src/client-rpc-fops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'xlators/protocol/client') diff --git a/xlators/protocol/client/src/client-rpc-fops.c b/xlators/protocol/client/src/client-rpc-fops.c index 80e6733b25d..15ffeb9aade 100644 --- a/xlators/protocol/client/src/client-rpc-fops.c +++ b/xlators/protocol/client/src/client-rpc-fops.c @@ -1283,7 +1283,7 @@ client3_3_removexattr_cbk (struct rpc_req *req, struct iovec *iov, int count, out: if (rsp.op_ret == -1) { if ((ENODATA == rsp.op_errno) || (ENOATTR == rsp.op_errno)) - loglevel = 0; + loglevel = GF_LOG_DEBUG; else loglevel = GF_LOG_WARNING; -- cgit