Project

General

Profile

Bug #15689

Confusing MDS log message when shut down with stalled journaler reads

Added by John Spray almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

https://www.mail-archive.com/ceph-users@lists.ceph.com/msg28758.html

Sending kill to MDS while it is stuck trying to replay journal causes it to proceed (and give a confusing error about bad journal version) instead of erroring out. The unwanted messages are:

2016-04-30 21:21:40.455902 7f9f83b9d700  4 mds.0.log Journal 300 recovered.
2016-04-30 21:21:40.455929 7f9f83b9d700  0 mds.0.log Journal 300 is in
unknown format 4294967295, does this MDS daemon require upgrade?

To avoid having OSD problems look like MDS problems, let's fix it.


Related issues

Copied to CephFS - Backport #15898: jewel: Confusing MDS log message when shut down with stalled journaler reads Resolved

History

#1 Updated by John Spray almost 8 years ago

  • Status changed from In Progress to Fix Under Review

#2 Updated by John Spray almost 8 years ago

  • Status changed from Fix Under Review to Pending Backport

Merged to master

#3 Updated by Nathan Cutler almost 8 years ago

  • Backport set to jewel

#4 Updated by Loïc Dachary almost 8 years ago

  • Copied to Backport #15898: jewel: Confusing MDS log message when shut down with stalled journaler reads added

#5 Updated by Loïc Dachary over 7 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF