From 84b344ef8a60d3a4800657dc4f5fc777be99e4b9 Mon Sep 17 00:00:00 2001 From: John Spray Date: Tue, 14 Mar 2017 22:17:36 +0000 Subject: [PATCH] client: specify inode in get_caps log message Otherwise when a client is stuck waiting for caps and periodically emitting this message, we have a hard time knowing which inode is involved. Signed-off-by: John Spray --- src/client/Client.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/client/Client.cc b/src/client/Client.cc index 8d711553fc8f..66760b987b2d 100644 --- a/src/client/Client.cc +++ b/src/client/Client.cc @@ -3111,7 +3111,7 @@ int Client::get_caps(Inode *in, int need, int want, int *phave, loff_t endoff) return 0; } } - ldout(cct, 10) << "waiting for caps need " << ccap_string(need) << " want " << ccap_string(want) << dendl; + ldout(cct, 10) << "waiting for caps " << *in << " need " << ccap_string(need) << " want " << ccap_string(want) << dendl; waitfor_caps = true; } -- 2.47.3