Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696227 - [RFE] print client IP in default debug_ms log level when "bad crc in {front|middle|data}" occurs
Summary: [RFE] print client IP in default debug_ms log level when "bad crc in {front|m...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RADOS
Version: 3.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 3.3
Assignee: Neha Ojha
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-04 11:28 UTC by Tomas Petr
Modified: 2019-04-11 07:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Tomas Petr 2019-04-04 11:28:00 UTC
Description of problem:
Ceph is checking the message from client in "Message *decode_message", there are few crc errors that can occur:
https://github.com/ceph/ceph/blob/v12.2.8/src/msg/Message.cc#L281
https://github.com/ceph/ceph/blob/master/src/msg/Message.cc#L288

From the default ceph-osd  log level of debug_ms we are not able to see which client has sent such message.
To get the client IP debug_ms=20 is needed.

It would speed up tracking the client, if the client IP would be printed with the "bad crc in {front|middle|data}"  error message in default log level.
Especially when the "bad crc in {front|middle|data}" can happen randomly.

Version-Release number of selected component (if applicable):
RHCS 2.x
RHCS 3.x


Note You need to log in before you can comment on or make changes to this bug.