Actions
Bug #41836
closedqa: "cluster [ERR] Error recovering journal 0x200: (2) No such file or directory" in cluster log"
% Done:
0%
Source:
Q/A
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
From: /ceph/teuthology-archive/pdonnell-2019-09-15_06:11:06-fs-wip-pdonnell-testing-20190915.030958-distro-basic-smithi/4308981/teuthology.log
Updated by Zheng Yan over 4 years ago
I think we can just whitelist the error 'Error recovering journal'
Updated by Zheng Yan over 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 30971
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to nautilus,mimic
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42423: mimic: qa: "cluster [ERR] Error recovering journal 0x200: (2) No such file or directory" in cluster log" added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42424: nautilus: qa: "cluster [ERR] Error recovering journal 0x200: (2) No such file or directory" in cluster log" added
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions