summaryrefslogtreecommitdiffstats
path: root/net/ceph/osd_client.c
diff options
context:
space:
mode:
authorSage Weil <sage@inktank.com>2012-07-30 16:26:13 -0700
committerSage Weil <sage@inktank.com>2012-07-30 18:16:03 -0700
commit756a16a5d53c072cd1f937b261641c1a3b53fdd7 (patch)
tree03cd42968c534a0f2407422d255b07bb0c956c8d /net/ceph/osd_client.c
parent43c7427d100769451601b8a36988ac0528ce0124 (diff)
downloadlinux-756a16a5d53c072cd1f937b261641c1a3b53fdd7.tar.bz2
libceph: be less chatty about stray replies
There are many (normal) conditions that can lead to us getting unexpected replies, include cluster topology changes, osd failures, and timeouts. There's no need to spam the console about it. Signed-off-by: Sage Weil <sage@inktank.com> Reviewed-by: Alex Elder <elder@inktank.com>
Diffstat (limited to 'net/ceph/osd_client.c')
-rw-r--r--net/ceph/osd_client.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/net/ceph/osd_client.c b/net/ceph/osd_client.c
index ad427e698890..42119c05e82c 100644
--- a/net/ceph/osd_client.c
+++ b/net/ceph/osd_client.c
@@ -2037,8 +2037,8 @@ static struct ceph_msg *get_reply(struct ceph_connection *con,
if (!req) {
*skip = 1;
m = NULL;
- pr_info("get_reply unknown tid %llu from osd%d\n", tid,
- osd->o_osd);
+ dout("get_reply unknown tid %llu from osd%d\n", tid,
+ osd->o_osd);
goto out;
}