From b8d5208f5c8945debe565ae72fea5a3795a44dfe Mon Sep 17 00:00:00 2001 From: shishir gowda Date: Wed, 25 Jul 2012 13:08:14 +0530 Subject: cluster/distribute: Suppress user xattr mismatch log message Changing the log-level to DEBUG. Xattr mismatch can occur when parallel setxattr's race, or when one of the bricks was down. A subsequent setxattr will fix the condition when all the subvols are up. In this case, the 'user.swift' xattr used by ufo was out of sync, but did not cause any other error. Change-Id: I6fdff78869b8ff72c305bbe122033e6c1d9d3cff BUG: 838197 Signed-off-by: shishir gowda Reviewed-on: http://review.gluster.com/3723 Tested-by: Gluster Build System Reviewed-by: Mohammed Junaid Reviewed-by: Vijay Bellur --- xlators/cluster/dht/src/dht-common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xlators/cluster/dht/src/dht-common.c b/xlators/cluster/dht/src/dht-common.c index 7ac08c659..5da0c10bb 100644 --- a/xlators/cluster/dht/src/dht-common.c +++ b/xlators/cluster/dht/src/dht-common.c @@ -69,7 +69,7 @@ dht_aggregate (dict_t *this, char *key, data_t *value, void *data) if (!ret && data_pair && value) { ret = is_data_equal (data_pair->value, value); if (!ret) - gf_log ("dht", GF_LOG_WARNING, + gf_log ("dht", GF_LOG_DEBUG, "xattr mismatch for %s", key); } } -- cgit