Actions
Bug #1006
closedclean up cmds journal-check mode
% Done:
0%
Source:
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
I'm not sure it should run in background instead of foreground.
Even if it should run in background, it should not take over the main MDS logs -- if you run with vstart and then start up a journal-check instance, it takes over the mds.a and mds.0 symlinks. :/
Updated by Greg Farnum about 13 years ago
- Translation missing: en.field_story_points set to 2
- Translation missing: en.field_position set to 637
Updated by Greg Farnum about 13 years ago
- Status changed from New to In Progress
- Assignee set to Greg Farnum
Okay, it's more broken than that -- somehow it ends up in standby-replay instead of oneshot-replay!
Updated by Greg Farnum almost 13 years ago
- Status changed from In Progress to Resolved
Well, it will still take over the mds.a symlink if you start it up as a pre-existing MDS, but you shouldn't do that. I made it so it does journal-check properly and runs in the foreground. We don't have the mds.0 symlinks anymore.
Updated by John Spray over 7 years ago
- Project changed from Ceph to CephFS
- Category deleted (
1) - Target version deleted (
v0.28)
Bulk updating project=ceph category=mds bugs so that I can remove the MDS category from the Ceph project to avoid confusion.
Actions