Skip to content
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

kraken: osd: do not send ENXIO on misdirected op by default #13253

Merged
merged 1 commit into from Apr 13, 2017

Conversation

liewegas
Copy link
Member

@liewegas liewegas commented Feb 3, 2017

In practice this tends to get bubbled up the stack as an error on
the caller, and they usually do not handle it properly.  For example,
with librbd, this turns into EIO and break the VM.

Instead, this will manifest as a hung op on the client.  That is
also not ideal, but given that the root cause here is generally a
bug, it's not clear what else would be better.

We already log an error in the cluster log, so teuthology runs will
continue to fail.

Signed-off-by: Sage Weil <sage@redhat.com>
(cherry picked from commit 923e7f5)

# Conflicts:
#	PendingReleaseNotes
@liewegas liewegas added this to the kraken milestone Feb 3, 2017
@smithfarm smithfarm changed the title osd: do not send ENXIO on misdirected op by default kraken: osd: do not send ENXIO on misdirected op by default Feb 21, 2017
@smithfarm
Copy link
Contributor

Jenkins retest this please (logs are gone)

@smithfarm smithfarm added the core label Feb 21, 2017
@smithfarm
Copy link
Contributor

@jdurgin This passed a rados suite at http://tracker.ceph.com/issues/19009#note-3 with one reproducible failure in rados/objectstore/objectstore.yaml that appears to be bluestore-related.

OK to merge?

@smithfarm smithfarm requested a review from jdurgin April 12, 2017 01:02
@smithfarm smithfarm merged commit 8a6e631 into ceph:kraken Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants