Project

General

Profile

Actions

Feature #602

closed

mds: handle corrupt/missing journals

Added by Sage Weil over 13 years ago. Updated over 7 years ago.

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

100%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:

Description

This probably means

- shutting down current instances, resetting cluster membership
- throwing out journals (or maybe not; but that's a separate feature)
- restarting cluster in single-mds, maybe with repair mode flag

Actions #1

Updated by Sage Weil over 13 years ago

  • Tracker changed from Tasks to Feature
Actions #2

Updated by Sage Weil over 13 years ago

  • Source changed from 0 to 3
Actions #3

Updated by Sage Weil over 13 years ago

  • Tracker changed from Tasks to Feature
  • Target version changed from 12 to v0.25
  • Parent task deleted (#86)
Actions #4

Updated by Sage Weil over 13 years ago

  • Translation missing: en.field_position set to 7
Actions #5

Updated by Sage Weil about 13 years ago

  • % Done changed from 0 to 60

see mds_reset branch.

Still need a process to reset the individual mds instances. This should:
- advance the journal header info to a new, unused region.
- do, or journal a single event that (on replay) will,
- update the mds inotable to avoid reusing ino's.
- zero out the mds session table.

Actions #6

Updated by Sage Weil about 13 years ago

  • Status changed from New to Resolved
  • % Done changed from 60 to 100

no repair flag, but journal discard and cluster reset are in place. not especially useful yet without the actual repair, though.

commit:548f329f03a640e292cd6ce762ffbacde3017e90

Actions #7

Updated by John Spray over 7 years ago

  • Project changed from Ceph to CephFS
  • Category deleted (1)
  • Target version deleted (v0.25)

Bulk updating project=ceph category=mds bugs so that I can remove the MDS category from the Ceph project to avoid confusion.

Actions

Also available in: Atom PDF