New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client: specify inode in get_caps log message #13966

Merged
merged 1 commit into from Apr 13, 2017

Conversation

Projects
None yet
2 participants
@jcsp
Contributor

jcsp commented Mar 14, 2017

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 john.spray@redhat.com

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 <john.spray@redhat.com>
@gregsfortytwo

This comment has been minimized.

Member

gregsfortytwo commented Mar 14, 2017

LGTM, but just think how much better a "CapTracker" on the MDS and OpTracker on the Client would be... ;)

@jcsp jcsp merged commit ccd6c81 into ceph:master Apr 13, 2017

3 checks passed

Signed-off-by all commits in this PR are signed
Details
Unmodifed Submodules submodules for project are unmodified
Details
default Build finished.
Details

@jcsp jcsp deleted the jcsp:wip-client-logmsg branch Apr 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment